Hi,
Alain Javier Guarnieri del Gesu wrote:
What is the state of affairs with the xmldb api itself. The
xmldb-api jar in the Xindice CVS is *not* the same as the one at
xmldb.org CVS. Where is the source?
The xmldb-api integrated with Xindice is not current either.
You can access the xmldb api and lexus source
via anonymous CVS using pserver authentication.
The CVS root is:
anoncvs@xxxxxxxxxxxxxxx:/raid/Repository
The password is "anoncvs".
Modules available for access are:
* xmldb
* xmldb/xapi
* xmldb/xupdate
* xmldb/sixdml
See: http://www.xmldb.org/projects.html and look for "CVS Repositories"
-Terry
Alain Javier Guarnieri del Gesu wrote:
* Terry Rosenbaum <Terry@xxxxxxxxxx> [2003-10-24 02:03]:
Michael Wechner wrote:
I recently fixed a bug within Lexus, but it seems that the Lexus
community at xmldb is kind of dead, or am I wrong on that?
Nevertheless I think xupdate and Lexus is very nice and it would be
great if Lexus could be part of some Apache (sub-)project or whatever.
Would that make sense?
?
Xindice does not even use the latest
available revision of Lexus.
The latest Lexus implementation in
the xmldb project's CVS is not quite compatible with
Xindice. I have been picking away at
that, working toward integrating the
latest Lexus version into Xindice.
In the latest version, there have been a few bug fixes and
the implementation has been made MT-safe.
I recentlly got a couple changes to that source
base (Lexus CVS head) made by contacting Jeroen Breedveld
jeroenb at x-hive dot com.
WRT your suggestion, perhaps discussing the Lexus project
status with Jeroen might be useful.
What is the state of affairs with the xmldb api itself. The
xmldb-api jar in the Xindice CVS is *not* the same as the one at
xmldb.org CVS. Where is the source?
| 
