Actually I wasn't volunteering, but if no one else is working on it then my company will likely tackle the problem in the coming months. I just didn't want to waste resources on work someone else was doing.
That would be cool. However, I'm not dead sure that the Xerces dependancy can be removed easily from the current codebase. I think that some of the Xindice internals rely on some Xerces code (not exposed by Jaxp). This is for sure the case with Xalan, on which the source relies for the XPath compiler (and, BTW, XUpdate too depends on Xalan).
BTW, any Xindice hackers out there who are looking for contract work implementing changes to Xindice?
Oh well... you have my e-mail, don't you? ;-)
Ciao,
-- Gianugo Rabellino CTO Pro-netics s.r.l. http://www.pro-netics.com
