Agile and Beyond - The Power of Aspirational Teams
Tim Mackinnon talks about the aspirations behind the Agile principles and practices, the desire to become efficient, to write quality code which does not end up being thrown away.
Tracking change and innovation in the enterprise software development community
Posted by Abhay Bakshi on Jul 03, 2007 11:28 AM
The first public review draft of JSR 225: XQuery API for Java has been posted for review. The spec (being led by Oracle) aims to provide standard programmatic access for XQuery implementations in Java. XQJ is a generic XQuery data access framework, which provides a uniform interface on top of a variety of different XQuery implementations....While the XQJ spec has been led by Jim Melton (Oracle), its JCP expert group involves members including Jason Hunter, DataDirect , BEA Systems et al. Industry leaders outside of JCP have also been following the XQJ specification, contributing ideas, and improving their own products for conformity. Michael Kay - creator of Saxon and author of XPath 2.0 Programmer's Reference - writes:
// establish a connection to the XQuery engine
XQConnection conn = xqds.getConnection();
// create an expression object that is later used
// to execute an XQuery expression
XQExpression expr = conn.createExpression();
// the XQuery expression to be executed
String es = "for $n in fn:doc('catalog.xml')//item " +
"return fn:data($n/name)";
// execute the XQuery expression
XQResultSequence result = expr.executeQuery(es);
// process the result (sequence) iteratively
while (result.next()) {
// retrieve the current item of the sequence as a String
String str = result.getAtomicValue();
System.out.println("Product name: " + str);
}
// free all resources allocated for the result
result.close();
// free all resources allocated for the expression
expr.close();
// free all resources allocated for the connection
conn.close();
...
It's the first new version for about a year, and the spec is developed under conditions of absolute secrecy, so I was interested to see what was going to be in it. I wasn't expecting too much, because most of my comments on the previous draft had been politely rejected (about 8 months after I submitted them, with no open discussion). Sure enough, they've tidied up quite a lot of little things, but the overall design hasn't changed much. (It's sufficiently incompatible, however, that most applications will have to be tweaked: not rewritten, but amended here and there.)
It's still uncompromisingly based on a client-server, connection-oriented model where the application lives on a different machine from the database (so 1980s!). ... prepared expressions are not thread-safe - you can't compile an expression and then run it in multiple threads simultaneously, because the XQPreparedExpression holds its own dynamic execution context.
Are there any good points? Yes, quite a few. The mapping of XPath values (the 19 primitive data types) to equivalent objects in Java is done reasonably well - much better than JAXP ... This version also has a full representation in Java terms of all XPath types ...The W3C XQuery specification and 8 related specifications (including XSLT 2.0 and XPath 2.0) were submitted to the W3C on June 8 2006. Many of them were updated on 23 January 2007. The industry has already begun embracing XQuery in their products, even JSR 170/Java Content Repositories use it as their standard query mechanism. InfoQ has been tracking development of XQuery specification, XQJ specification, and the implementations.
Still, I think one can do better. ...
Hibernate without Database Bottlenecks
WebSphere Virtual Enterprise 3 minute demo
The End of Middleware: Freedom from IT Stacks as we know it
JProbe Freeware – Eclipse Plugin for efficient memory analysis and diagnosis
Gamma's Jazz platform's first implementation: Rational Team Concert (Trial Download)
Thanks for another very interesting article. Keep up the good work. Regards Pozycjonowanie Tom
Interesting Article, thank you for sharing your thoughts.
Tim Mackinnon talks about the aspirations behind the Agile principles and practices, the desire to become efficient, to write quality code which does not end up being thrown away.
Brian Goetz discusses the difficulties of creating multithreaded programs correctly, incorrect synchronization, race conditions, deadlock, STM, concurrency, alternatives to threads, Erlang, Scala.
Often the hardest part of changing technologies is language syntax differences. This new article provides Java developers with a transition guide to Actionscript which forms the foundation of Flex.
Neal Ford talks about having multiple languages running on one of the two major platforms: Java and .NET. He also presents the advantages offered by Ruby compared to static languages like Java or C#.
David Anderson talks about the history of Agile, the current status of it and his vision for the future. The role of Agile consists in finding ways to implement its principles.
Nick Sieger talks about the future of JRuby, Java Integration, and his work on JEE deployment tools for Ruby on Rails like Warbler.
Rustan Leino and Mike Barnett of Microsoft Research discuss the technology in Spec# and its futures.
Henrik Kniberg talks about 10 possible reasons to fail while doing Scrum and XP. Maybe the team does not have a definition of what Done means to them, or they don't know what their velocity is.
2 comments
Reply