[ebxmlms-general] library conflicts using JBoss 3.2.7

[julien <ju...@ni...>]

Hello all,

 I am attempting to deploy Hermes MSH 1.0.0.1 under JBoss 3.2.7 and I get this error at loading time:

[...]

14:16:06,571 INFO  [TomcatDeployer] deploy, ctxPath=/msh, warUrl=file:/usr/local/install/dev/jboss/jboss-3.2.7/server/default/deploy/msh.war/
14:16:09,048 INFO  [STDOUT] Info: using property file in /usr/local/install/dev/jboss/jboss-3.2.7/msh.properties.xml
14:16:09,445 INFO  [STDOUT] [10001] Initialization error
Exception: hk.hku.cecid.phoenix.message.handler.InitializationException
Message: [10501] Default MessageFactory cannot be instantiated
Exception: javax.xml.soap.SOAPException
Message: Failed to create MessageFactory: org.apache.axis.soap.MessageFactoryImpl
14:16:09,453 INFO  [Engine] StandardContext[/msh]Marking servlet msh as unavailable
14:16:09,454 ERROR [Engine] StandardContext[/msh]Servlet /msh threw load() exception
javax.servlet.ServletException: Error instantiating servlet class hk.hku.cecid.phoenix.message.handler.MessageServiceHandler

[...]

14:16:09,480 ERROR [Engine] ----- Root Cause -----
hk.hku.cecid.phoenix.message.handler.MessageServiceHandlerException: [10501] Default MessageFactory cannot be instantiated
Exception: javax.xml.soap.SOAPException
Message: Failed to create MessageFactory: org.apache.axis.soap.MessageFactoryImpl
        at hk.hku.cecid.phoenix.message.handler.MessageServiceHandler.<init>(Unknown Source)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
        at java.lang.Class.newInstance0(Class.java:350)
        at java.lang.Class.newInstance(Class.java:303)

[...]


 Apparently JBoss is trying to use org.apache.axis.soap.MessageFactoryImpl.class (found in jboss-3.2.7/server/all/deploy/jboss-net.sar/axis-ws4ee.jar) instead of com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.class (from jboss-3.2.7/server/default/deploy/msh.war/WEB-INF/lib/saaj-ri.jar).

 Axis is coming with JBoss, and a simple removal of the jboss-net.sar directory won't work as it seems to be required.
 Does anyone have any idea how to force the right library to load instead of the one from Axis?

 Thanks for your help!

 Julien