Page 1 of 1

JBoss EAP 6.2 and Xalan module dependency couldn't resolved

PostPosted: Mon Oct 13, 2014 7:22 pm
by AndreasN

I have a setup running with an additional module with its dependencies but would like to use the already existing xalan module "org.apache.xalan" but there is an ugly exception in the server log explaining:

javax.xml.transform.TransformerFactoryConfigurationError: Provider org.apache.xalan.processor.TransformerFactoryImpl not found
Caused by: java.lang.ClassNotFoundException: org/apache/xalan/processor/TransformerFactoryImpl

The libs of the xalan module contains the desired class, the jar file is named "xalan-2.7.1-redhat-3.jar".

Ok, I can add the "xalan-2.7.1.jar" as resource instead of module, but its not what I want.
The docx version is 3.2.0 and the module itself is loaded by the jboss-deployment-structure.xml

What goes wrong?

Kind regards,

Code: Select all
<module xmlns="urn:jboss:module:1.1" name="org.docx4j-compat">

        <resource-root path="docx4j-3.2.0.jar"/>
        <resource-root path="xmlgraphics-commons-1.5.jar"/>
      <resource-root path="xalan-2.7.1.jar"/>
        <resource-root path="serializer-2.7.1.jar"/>
      <resource-root path="jaxb-xmldsig-core-1.0.0.jar"/>

        <module name=""/>
      <module name="org.apache.commons.logging"/>
      <module name="org.slf4j"/>
      <module name="org.apache.xalan"/>
      <module name="sun.jdk" />
         <system export="true">
               <path name="com/sun/xml/internal/bind/marshaller" />
      <module name="com.sun.xml.bind" />
      <module name="javax.xml.bind.api"/>
      <module name="javax.api" />


The original xalan module setup;

Code: Select all
<module xmlns="urn:jboss:module:1.1" name="org.apache.xalan">

        <resource-root path="serializer-2.7.1-redhat-3.jar"/>
        <resource-root path="xalan-2.7.1-redhat-3.jar"/>
        <!-- Insert resources here -->

        <module name="javax.api"/>