I just made it in having a working version of 1.1 with Xupdate. It had been a day of struggle and I had to recompile by hand a lot of xmldb stuff, but it looks like we have a viable setup.
This is simply great! I started yesterday evening to look at it but you were quicker.
Have you upgraded xmldb to xalan-2.4.1? I think I don't have to tell you to submit a patch to the xmldb guys :-) It's important to know that Xindice uses a patched version of xmldb. I've submit a patch but they haven't applied it so far (looking for another, cleaner solution).
Well... yes and no. What I did was "simply" to:
1. remove infozone-tools from our CVS;
2. recompile xmldb-common with our Xalan/Xerces. I had to exclude the Xalan1 package from the compilation since it was, of course, just failing (but we don't use it anyway). I also hardcoded the xalan2 factory as the default factory in xmldb-commons, but this can be changed;
3. recompile xmldb-xupdate with the new Xerces/Xalan (I had no problem with that);
4. put the generated xmldb-xupdate/common jars in our lib dir.
5. patch our XUpdate implementation: s/infozone.tools/xmldb.commons/g was enough IIRC;
6. patch our build.xml to include the (patched) xmldb-commons/xmldb-xupdate jars;
7. recompile Xindice, laund my trusted Jelly :-), run the XUpdate guide example, get "4 entries updated" as a result, rejoice. :-)
That was it (of course IIRC), I didn't really understand what your DatabaseManager patch is about (regarding XUpdate). Should I go on and commit all the changes so that you might try them out?
Ciao,
-- Gianugo
