IBM and Oracle have announced the Early Draft Review for JSR 225, XQuery API for Java.
- Posted by: Dion Almaer
- Posted on: May 26 2004 12:01 EDT
This specification aims to develop a common API that allows an application to submit queries conforming to the W3C XQuery 1.0 specification and to process the results of such queries.
It is great to see these new Early Drafts, that are part of the more open JCP.
Go to the JSR 225: XQuery API for Java home page
Download the JSR 225 Early Draft Review (review closes on 9th July 2004).
Are you using XQuery in the real world?
I've used it in the Weblogic Integration product where it is the vehicle for transformation controls. I really like it, the FLWOR syntax seems quite natural to write. To contrast with XSLT, I think XSLT is more useful in document based scenarios for instance the classic XML -> HTML transformation. XQuery is more useful in transforming data. For example if you had a file of XML order records and you wanted to transform those orders for a different system, XQuery would be perfect.
To contrast with XSLT, I think XSLT is more useful in document based scenarios for instance the classic XML -> HTML transformation. XQuery is more useful in transforming data.
LOL. Yeah, I think a screwdriver is more useful in screw based scenarios and a hammer is better in nail transposing nails.
XQJ is to XQuery what JDBC is to SQL. Even though XQuery is still a W3C
draft, the release of this early draft shows that major vendors in the Java
and J2EE world consider XML and XQuery as critical technologies. Note that
XQuery is not limited to querying native XML databases, but can also be used
to query other types of datasources, such as relational databases, plain XML
documents or Web Services. You can have a look at the ObjectWeb XQuark project
(http://xquark.objectweb.org) to have an example of what can be achieved
with XQuery. XQuark intends to support XQJ when it will be officially
released. A similar API, called XML/DBC, is already available in XQuark.
XQuery (SQL for XML) is going to be huge, by leveraging all that relational training for XML.
Here's the list of implementations (bottom half):
I've tried Saxon (extended to include XQuery), and it seems to works well(http://saxon.sourceforge.net/)
It's extremely powerful for data extraction and transformation to process any XML data source, such as JSX (www.jsx.org), which serializes any object graph to XML).