1 Reply Latest reply on Jul 10, 2003 3:04 AM by Bernd Zeitler

    Deploying Xalan under JDK 1.4 with Servlet 2.3 Classloading

    Bruce Wilson Newbie

      I'm currently deploying Xalan and Xerces in JBoss 3.0.7 and
      JDK 1.4.1 using "-Djava.endorsed.dirs" to point to a
      separate directory where the Xalan and Xerces jar files are
      located.

      The enterprise application that I'm working on has 3
      different web applications - a GUI and two SOAP interfaces.
      What would be the best way to deploy different versions of
      Xalan/Xerces for each of the different web apps ? Does it
      work to use Servlet 2.3 classloading (i.e., set
      Java2ClassLoadingCompliance "false" in
      jbossweb.sar/META-INF/jboss-service.xml) ? In other words,
      with Servlet 2.3 classloading enabled, will the web
      applications each find the version of Xalan deployed in
      their respective WEB-INF/lib/ directories, even though the
      core JDK has a "endorsed" version in rt.jar ? I was
      wondering whether anyone else had experience with this and
      had it working OK.

      Thanks in advance,

      Bruce

        • 1. Re: Deploying Xalan under JDK 1.4 with Servlet 2.3 Classload
          Bernd Zeitler Expert

          This approach should work with every deploymemt unit for your version of JBoss (.jar, .war, .ear, .sar):

          You can use the loader-repository and the loader-repository-config tag in your JBoss specific deployment descriptor. This tells JBoss to use an own repository for this unit and to turn the direction of delegeation from child to parent. Example:
          [pre]
          <loader-repository>bean1.company.com:loader=bean1.jar
          <loader-repository-config>java2ParentDelegation=false</loader-repository-config>
          </loader-repository>
          [/pre]

          Greetings,
          Frito