Deploying AXIS2 (1.5) on JOnAS 5.1.5

"Hans J. Prueller" <[email protected]>
Newsgroups gmane.comp.java.objectweb.jonas
Organization LBS logics GmbH
Message-ID <1295166470.2310.4.camel@kodos>
Hi all,

we have developed WebServices based on AXIS2 (1.5.1)  that are deployed
on JOnAS 4.10 as separate .war file currently. This works very smooth on
JOnAS 4.x
but when we try to deploy the .war file to JOnAS 5.1.5, we get the
following error:

2011-01-16 09:20:02,162 : WARDeployer.doDeploy : Deploying axis2.war
2011-01-16 09:20:05,511 : StandardContext.listenerStart : Exception
sending context initialized event to listener instance of class
com.sun.faces.config.ConfigureListener
java.lang.ClassCastException:
org.apache.xerces.jaxp.SAXParserFactoryImpl cannot be cast to
javax.xml.parsers.SAXParserFactory
	at javax.xml.parsers.SAXParserFactory.newInstance(Unknown Source)
	at com.sun.faces.config.ConfigureListener
$WebXmlProcessor.getConfiguredFactory(ConfigureListener.java:513)
	at com.sun.faces.config.ConfigureListener
$WebXmlProcessor.scanForFacesServlet(ConfigureListener.java:485)
	at com.sun.faces.config.ConfigureListener
$WebXmlProcessor.<init>(ConfigureListener.java:459)
	at
com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:135)
	at
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4135)
	at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4630)
	at
org.ow2.jonas.web.tomcat6.JOnASStandardContext.start(JOnASStandardContext.java:281)

Seems that there is a class conflict regarding the XML parsers. 

The axis2.war file already contains a jonas-web.xml in WEB-INF directoy,
with the setting:


<jonas-web-app xmlns="http://www.objectweb.org/jonas/ns"
	  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	  xsi:schemaLocation="http://www.objectweb.org/jonas/ns
	  http://www.objectweb.org/jonas/ns/jonas-web-app_4_2.xsd" >

   <java2-delegation-model>false</java2-delegation-model>
   
</jonas-web-app>


Which should avoid classloader conflicts -- but it seems in this case it
has no effect.


Any ideas how we could solve / workaround this problem ?


regards,
Hans
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.