I think the reason for this request for Xerces 2 / JDK 1.4 is so that
we can use XMLC unmodified in a standard containers without putting
into the patched Xerces somewhere. With that in mind, I'd like to
pointing out the following:
DOM Level 3 API. XMLC uses DOM Level 3 API in some of the place.
Richard has put into reflection to deal with this but it only solve
half the problem. Xerces 2 comes with only DOM Level 2 package
(org.w3c.dom) as well as JDK 1.4. XMLC would have problem even compiled
with DOM Level 3 API.
Moving XMLC to Xerces 2 would involve more then just checking bug fixes
in Xerces.
David Li
On Saturday, Jan 18, 2003, at 07:52 Asia/Shanghai, Mark Diekhans wrote:
David Corbin <dcorbin@xxxxxxxxxxxxxx> writes:
I'd certainly like to see this. Mostly to get away from patched
versions of "standard" libraries. The patches to xerces are big black
eye that shows up everytime I have to defend XMLC against JSP....
This requires someone going though the patches and determining which
are still
bugs in xerces, migrating those that are to the current xerces and
submitting
them to the xerces folks. Many are to the HTML DOM, which I don't
think has
change much. One isn't really a xerces bug, but something that should
be
changed in XMLC. All of the patches are documented.
None of this is really all that hard, just time consuming. If anyone
wants to
take this on, I will be happy to advise. I wish I had the time to
actually
do it, but I don't, and will not in the foreseeable future.
But this is really the only way it's going to happen.
Mark
_______________________________________________
XMLC mailing list
XMLC@xxxxxxxxxxx
http://www.enhydra.org/mailman/listinfo.cgi/xmlc
| 