-
1. Re: Question on using xerces in JBoss 3.0
cvolk Mar 25, 2003 10:27 AM (in response to pittpensfan01)This is not a full answer, but I do have the JAXP 1.22 version of Xerces from Sun's WSDK 1.1 installed and working. Don't forget to add the following system properties to your JBoss startup script:
javax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
javax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl
javax.xml.transform.TransformerFactory=org.apache.xalan.processor.TransformerFactoryImpl
I have not experienced problems relating to hardcoded Crimson references (not that that fully proves anything).
Also, for Xerces 2 there are 2 jar files (xercesImpl.jar and xmlParserAPIs.jar), not one, and two files to replace (crimson.jar and jaxp.jar).
If you use the WSDK, move out the same two files and move in the following 5 jars:
dom.jar
sax.jar
xalan.jar
xercesImpl.jar
xsltc.jar
You apparently don't need to copy in jaxp-api.jar
I also moved xalan.jar out of $JBOSS_HOME/server/[instance]/lib.
Hope this is useful. If you've already covered all this, then my apologies for wasting your time ;-) -
2. Re: Question on using xerces in JBoss 3.0
juhalindfors Mar 30, 2003 8:20 AM (in response to pittpensfan01)The chances of backporting the changes detailed in the note to 3.0.x are slim. However, I think you will only be affected by this in 3.0.x series if you're using the JBossMX ModelMBean implementation.