> what was the motivation for building a patched version? > is there a process by which the patches can be moved back upstream to the > xmldb api initiative maintainers?
IIRC there's a problem in how Xindice registers itself to the DatabaseManager. The general idea expressed by the xmldb implementation is that you have to register each Database object separately. Typically, Xindice would have to register the XML-RPC and Embed Database separately. However, Xindice uses a "super-Database" (o.a.x.client.xmldb.DatabaseImpl) that acts like a facade to both XML-RPC and Embed databases. And only this DatabaseImpl is registered for the two other Databases. I can understand why it was done that way (e.g. simplification of the admin client) but I always found quite strange that the clients (by sending the first request to the database) is dictating what the server should be doing (or what type of database (xml-rpc, embed) should be started). The best option would be to simply delete the o.a.x.client.xmldb.DatabaseImpl. I contacted the xmldb group several months ago and explained the situation but I don't think they changed the API. And I think they shouldn't. -Vladimir -- Vladimir R. Bossicard Apache Xindice - http://xml.apache.org/xindice
