OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: [xml-dev] Early Draft Review: XQuery for Java (JSR 225)

[ Lists Home | Date Index | Thread Index ]

> What do you mean by XQJ client ? Is it the driver, which implements the
> XQJ API, takes the queries and sends them off to the server ?
> Or do you mean the code written by the XQJ user ?

The XQJ client uses a driver to connect and submit queries to an XQuery engine.
A typical scenario is a client-server architecture with the query engine running
on a separate machine from clients that submit queries across the wire (in this
case XQJ clients). The XQuery server and XQJ client execute on separate
computers, or in separate processes if they reside on a single computer.

> Any Java byte arrays can be "serialized" to a sequence of bytes (just
> don't call the "serialize" method, but write something like
> "toMyCustomBLOB()").

1. The client (XQJ or otherwise) has to be pass the query to the XQuery engine
using a mutually-understood format. If Java clients are not passing query
strings, then there needs to be a spec for queries represented as CustomBLOBs.

2. Someone building an XQuery server will often prefer a language-neutral
solution for servicing clients. Come one, come all -- Java clients, C#, Perl,

3. If we must choose between elegance and interoperability, my vote is for
interoperability. SOAP and XML RPCs emerged in part because of interoperability
issues with COM+ and CORBA. XQuery servers, like HTTP servers, will serve a
broader audience if they employ language-neutral and platform-neutral


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS