I got this to work:
$ ls
xml.jar xerces.jar tmp
$ cd tmp
$ jar -xf ../xml.jar
$ jar -xf ../xerces.jar
$ jar -cf ../xml.jar *
Ie. overlay the contents of xml.jar onto xerces.jar. I then use this as the xml.jar in JBOSS_HOME/lib. It works, but is kind of messy, and I don't think it meets your requirement of using an unmodified xerces.jar.
Tom
--
Tom Cook
Systems Development
Australian Submarine Corporation
Mersey Road
Outer Harbour
+61 8 8348 7645
"From the instant I picked your book up, until the moment I put it down, I was convulsed with laughter. I fully intend to read it one day."
- Groucho Marx
-----Original Message-----
From: Roger Spreen [SMTP:[EMAIL PROTECTED]]
Sent: Thursday, January 11, 2001 1:44 PM
To: jBoss
Subject: [jBoss-User] running xalan & xerces in JBoss pre-2.1
If you're trying to use Xalan & Xerces with the latest JBoss sources
(pre-2.1), you'll probably run into problems due to the "xerces vs. jaxp"
problem.
We're using xalan/xerces in our beans, and the collisions between
parser.jar (from Jaxp, which JBoss uses for its XML parsing) and xerces.jar
(which xalan uses) causes classloader issues when doing
transformations. To make things work for us, it required:
- removing org.* classes from parser.jar. (removing the xerces-jaxp overlap)
- removing xml.jar from lib/ext (not needed)
- including xerces.jar in the initial Jboss startup classpath (so that
JBoss can work with its config files)
If you have a cleaner solution, I'd love to hear it - I wanted a solution
that (a) allowed us to use standard xalan & xerces libraries without
modification, and (b) didn't require any modifications to JBoss source code.
Hope this helps,
Roger
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
