The resolver and serializer are separate components that are released from the XML Commons [1] and Xalan [2] projects. Xerces depends on them for XML Catalog and DOM Level 3 serialization support. They can be used on their own.
[1] http://xml.apache.org/commons/ [2] http://xalan.apache.org/ Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: [EMAIL PROTECTED] E-mail: [EMAIL PROTECTED] David M Williams <[EMAIL PROTECTED]> wrote on 02/02/2007 03:13:22 AM: > > I work in the Webtools Project in Eclipse, and have for years > produced Xerces plugins for each release of Xerces. (Which in turn is > used by other Eclipse plugins). > > I'm about to do it again, but a little differently ... using an > "exploded jar" in an OSGi bundle. In the simplest case, I'd just > create a bundle for > every jar in Xerces. This especially makes sense in the cases of > xml-apis.jar and xercesImpl.jar since, by design, someone may want > to use the APIs, but > provide their own implementation. > > The other two jars are less obvious to me, resolver.jar and the > "new" serializer.jar. Are these jars separate for some conceptual or > distribution reason? > For example, do some people use only the resolver all by itself? Or, > do they "swap in" their own version of resolver.jar? Or, are they > separate just due to > historical and build reasons, and that conceptually, they could just > be part of xercesImpl.jar? > > Thanks, --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
