There is an XQuery service already. The interface was based on the work done
by the eXist group. A reference implementation is missing though.
I think your connection -> database idea is good. Do you have time to create a
patch for this change?
tisdagen den 4 januari 2005 07.25 skrev Ronald Bourret:
> This would also duplicate work being done elsewhere. JSR 225  is a
> Java API for executing XQuery queries against various data sources,
> including native XML databases. Oracle and IBM made the original
> proposal, and the working group includes people from Software AG, Ipedo,
> BEA, DataDirect, Mark Logic, and Sybase -- quite a bit of technical and
> marketing weight.
> I think what really needs to be done with XML:DB is to clean up some of
> the real weirdnesses (like connecting to a collection, rather than a
> database) and omissions (like an XQuery service).
> -- Ron
>  http://jcp.org/en/jsr/detail?id=225
> Uche Ogbuji wrote:
> > On Wed, 2004-10-20 at 21:42 +0200, Per Nyfelt wrote:
> >>One thing that I have ben thinking about is the language neutrality of
> >> the api. Now that XQuery covers most of the needs in terms of providing
> >> an XML based way to interact with XML data that can be stored in various
> >> ways maybe focusing the api on Java or perhaps at least object oriented
> >> languages could allow us to simplify and clean up some things (such as
> >> taking advantage of method overloading and allowing for a more OO feel
> >> to the api rather than current, sometime very string focused, approach).
> > I think this would be a mistake. Part of the reason I stay interested
> > in XML:DB is that I have a strawman implementation for our own OSS
> > Python XML repository, 4Suite (I've already implemented a Python XML:DB
> > in a closed source project for a client). If it moves to a Java spec, I
> > would personally look to fork the project.