Hi,
The problem here is both Jboss & Axis have their own SAAJ Implementation.
What is the version of Jboss & Axis2 your using?
Do you intend to run other applications on this server as well?
You do not need to move several jars.The classes you need are located
inside axis2-saaj-<version>.jar.
/sumedha
Lorenzo wrote:
Hi all,
i have this problem:
i deployed mi axis2 app on jboss into a .ear
myapp.ear
|- lib
|- mdb.jar
|- META-INF
|- manifest.mf
|- ejb-jar.xml
|- jboss.xml
|- web.war <-- axis2
|- META-INF
|- manifest.mf
|- WEB-INF
|- modules
|- mymodule.mar
|- services
|- myservice.aar
|- conf
|- axis2.xml
|- web.xml
I tryed to get a org.apache.axis2.saaj.SOAPMessageImpl from a
MessageContext but i get a java.lang.ClassCastException because it use
MessageFactoryImpl of jboss instead of Axis2.saaj one so i get a
org.jboss.ws.soap.SOAPMessageImpl instead
org.apache.axis2.saaj.SOAPMessageImpl.
I can avoid this moving some axis2 lib from myapp.ear/lib to
myapp.ear/web.war/WEB-INF/lib (seems that there jars have higher
priority then others..) but seems that now Axis2 don't get libs
specified into manifest and i need to use the same libs used by mdb.jar
I hope i was clear :)
Any suggestion is appreciate,
thx Lorenzo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
