At 04:11 PM 9/15/2003 -0400, you wrote:
In what areas will XMLC 2.2 require me to rebuild code that uses XMLC 2.1? I
know that (alledgedly) the error handling interface is different, but I don't
use that in the project I'm most worried about.
Hmm.... nowhere that I know of? Most of XMLC's changes have been
internal. You can now take advantage of deferred parsing, but the old ways
shouldn't break. Oh, there is one thing. If you have been using methods
in the DOM that exist only in the unofficial version of the DOM API (which
was part of h;tml dom level2, but in the old level 1 package namespace)
that were included in Xerces-1.4.4 (and j2sdk1.4.x, unfortunately), then
you'll have to watch out. To test this, build your code under Ant
(including xml-apis.jar and xercesImpl.jar in ANT_HOME/lib) and use
XMLC-2.2 instead of XMLC-2.1. Make sure that xerces-1.4.4 is nowhere in
your build classpath. If you don't get compile errors, you are most likely
just fine. I really can't think of anything else that would break things,
except that you now have to make sure that xml-apis.jar and xercesImpl.jar
(from Xerces2) are in the classpath for build-time and runtime.
Jake
David
_______________________________________________
XMLC mailing list
XMLC@xxxxxxxxxxx
http://www.enhydra.org/mailman/listinfo.cgi/xmlc
| 