[From: [EMAIL PROTECTED] <Shane_Curcuru at lotus.com>]
> See this thread on general@xml and it's previous documents:
> http://marc.theaimsgroup.com/?l=xml-apache-general&m=100652621822282&w=2
> You'll obviously have to ask the Xerces-J community about what their plans
> are for .jar file packaging, but from that thread I think they're going to
> adopt a similar model (xalan/xerces.jar are just implementation classes,
> xml-apis.jar are just externally-defined standards based files and
> interfaces)
I think that this is a good thing in general, but it can be a source of
confusion and frustration. For example, the DOM API included with Xerces
1.4.4 has DOM3 experimental methods in the interfaces, so other applications
won't necessarily build against it. If you're going to go with an unbundled
strategy, then separate JARs for the different APIs would be nice:
DOM2.jar, SAX2.jar, etc. It can make for a long classpath, but it's the
clearest alternative.
-- Paul
