On Dec 6, 2005, at 12:09 PM, Peter Lynch wrote:
The piccolo classes have their packages changed so that there will
be no conflict with the real piccolo classes:
$ jar -tf xbean.jar | grep piccolo
org/apache/xmlbeans/impl/piccolo/
org/apache/xmlbeans/impl/piccolo/io/
org/apache/xmlbeans/impl/piccolo/util/
org/apache/xmlbeans/impl/piccolo/xml/
org/apache/xmlbeans/impl/piccolo/io/CharsetDecoder.class
org/apache/xmlbeans/impl/piccolo/io/FileFormatException.class
org/apache/xmlbeans/impl/piccolo/io/IllegalCharException.class
org/apache/xmlbeans/impl/piccolo/util/CharStringConverter.class
org/apache/xmlbeans/impl/piccolo/util/DuplicateKeyException.class
Okay, I think I'm starting to understand. XmlBeans uses modified
versions of JAM and Piccolo, and these are injected into xbean.jar
with different package names to avoid conflict. That means as long as
I don't need to recompile xbean.jar, I can "throw away" the source
JARs (jam-0.1.0-src.jar, piccolo*). Is that right?
As for the binary JARs (saxon8.jar, jsr173*), they are still
required, but because they are unmodified by XmlBeans, I could simply
use the official distributions instead of the ones bundled with
XmlBeans, correct?
I guess the only thing I'm not understanding now is xcresolver. This
is included as a source file in XmlBeans, so I assume it is modified
for XmlBeans in some way. But instead of ending up in xbean.jar with
modified package names, it gets its own JAR (resolver.jar) with an
unmodified namespace. Wouldn't that cause a conflict with a user's
existing installation of Apache Commons Resolver?
Thank you,
Trevor
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
