2 Replies Latest reply on Mar 30, 2003 8:20 AM by Juha Lindfors

    Question on using xerces in JBoss 3.0

    Tom Newbie

      Hi.

      I'm trying to use the xerces parser in JBoss 3.0. I was going to remove any references to crimson in JBoss 3.0 by swapping out the crimson.jar file with the xerces jar files and indicate the changes in the startup script.

      However, I've been looking at the source and there are three files that require crimson. It appears to me that the command line switch settings will not have any affect on whether crimson gets used or not.

      The classes are:
      JBossXMBean10.java
      XMBeanMetaData.java
      XMLMetaData.java

      This is the code in question:
      // FIXME FIXME FIXME
      // the SAX driver is hard coded here due to conflicts with the JAXP/Crimson
      // version in the testsuite build system and the JAXP/crimson versions required
      // by the JDOM Beta 7 implementation (JAXP 1.1 & crimson 1.1)
      //
      // the driver class (and validation) should be configurable by the client
      //
      SAXBuilder builder = new SAXBuilder("org.apache.crimson.parser.XMLReaderImpl");

      I've looked at this bug...
      https://sourceforge.net/tracker/?func=detail&aid=561588&group_id=22866&atid=381174

      But the problem still seems to exist. It looks like the fix may be on the 3.2 branch. Is there any chance of getting this fixed for 3.0.x?

      Thanks in advace!
      Tom

        • 1. Re: Question on using xerces in JBoss 3.0
          Christopher Volk Newbie

          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
            Juha Lindfors Master

            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.