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
etc....
-Peter
Trevor Harmon wrote:
[snip]
Hmm, then it sounds like a system-wide installation of XmlBeans is
impossible. In other words, if I put xbean.jar in my CLASSPATH, and I
also have the "real" JAM or Piccolo JARs in my CLASSPATH, then
something's going to break. For instance, apps that require the real
JAM might find the XmlBeans JAM, or XmlBeans might grab the real JAM,
depending on the order of JARs in the CLASSPATH. Either way, something
can go wrong.
[
Trevor
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
