Query evaluation techniques for large databases
ACM Computing Surveys (CSUR)
An early look at XQuery API for Java™ (XQJ)
ACM SIGMOD Record
The BEA streaming XQuery processor
The VLDB Journal — The International Journal on Very Large Data Bases
System RX: one part relational, one part XML
Proceedings of the 2005 ACM SIGMOD international conference on Management of data
Native Xquery processing in oracle XMLDB
Proceedings of the 2005 ACM SIGMOD international conference on Management of data
XQuery implementation in a relational database system
VLDB '05 Proceedings of the 31st international conference on Very large data bases
Data delivery in a service-oriented world: the BEA aquaLogic data services platform
Proceedings of the 2006 ACM SIGMOD international conference on Management of data
Towards a physical XML independent XQuery/SQL/XML engine
Proceedings of the VLDB Endowment
| Hi-index | 0.00 |
Just as SQL is a declarative language for querying relational data, XQuery is a declarative language for querying XML. JDBC provides a standard Java API to interact with a variety of SQL engines to declaratively access and manipulate data stored in relational data sources. Similarly, XQJ provides a standard Java API to interact with a variety of XQuery engines to declaratively access and manipulate XML data in variety of XML data sources. XQJ, also known as JSR 225, is designed through the Java Community Process (JCP) [20]. The XQJ specification defines a set of Java interfaces and classes that enable a Java program to submit XQuery expressions to an XQuery engine operating on XML data sources and to consume XQuery results. In this article, we discuss the XQJ APl's technical details with its similarities; and differences from JDBC, the design philosophies and goals for XQJ, the implementations strategies of XQJ in variety of XQuery engines and their operating environments, and the possible future of XQJ.