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]
