I was able to track it down to the fact that a WebSphere jar (com.ibm.ws.runtime_6.1.0.jar) included a lightweight version of the WSDL reference implementation that did not contain any of the extensibility elements provided by the WSDL4J implementation. Unfortunately due to the class clash with these classes in the server class loader the WSDL4J libraries were not getting loaded in the servicemix WAR classloader even though I had set the classloading to self first.
Does anyone have any suggestions for how to combat this without adding the WSDL4J implementation to the WebSphere jar? (which btw works) -----Original Message----- From: Grant Mcdonald [mailto:[EMAIL PROTECTED] Sent: Thursday, 1 February 2007 1:18 PM To: [email protected] Cc: Ramon Buckland Subject: Running ServiceMix as a WAR inside Websphere 6.1 Hi, I am trying to run servicemix as an embedded war file (using a modified version of the servicemix-web sample) in WebSphere 6.1.00 with the following config: <beans xmlns:sm="http://servicemix.apache.org/config/1.0";> <!-- the JBI container --> <sm:container id="jbi" rootDir="/opt/cbis-home-1.0.4/wdir" installationDirPath="/opt/cbis-home-1.0.4/install" deploymentDirPath="/opt/cbis-home-1.0.4/deploy" flowName="seda" useMBeanServer="true" createMBeanServer="true" dumpStats="true" statsInterval="10" transactionManager="#transactionManager"> <sm:activationSpecs> </sm:activationSpecs> </sm:container> </beans> I end up getting the following very unspecific error: 12:33:48,462 | WARN | Timer-4 | AutoDeploymentService | ramework.AutoDeploymentService 604 | Automatic install of /opt/cbis-home-1.0.4/deploy/cbis-extract-sa-1.0.4.2.zip failed javax.resource.spi.work.WorkCompletedException: Unknown error, error code: 0 at org.apache.geronimo.connector.work.WorkerContext.run(WorkerContext.java: 323) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Thread.java:797) Caused by: java.lang.IncompatibleClassChangeError at org.apache.servicemix.http.tools.PortTypeDecorator.decorate(PortTypeDeco rator.java:107) at org.apache.servicemix.http.HttpEndpoint.overrideDefinition(HttpEndpoint. java:215) at org.apache.servicemix.soap.SoapEndpoint.loadWsdl(SoapEndpoint.java:233) at org.apache.servicemix.soap.SoapEndpoint.activate(SoapEndpoint.java:342) at org.apache.servicemix.common.ServiceUnit.start(ServiceUnit.java:50) at org.apache.servicemix.common.BaseServiceUnitManager.start(BaseServiceUni tManager.java:149) at org.apache.servicemix.jbi.framework.ServiceUnitLifeCycle.start(ServiceUn itLifeCycle.java:103) at org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start(Servi ceAssemblyLifeCycle.java:130) at org.apache.servicemix.jbi.framework.DeploymentService.start(DeploymentSe rvice.java:374) at org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive( AutoDeploymentService.java:297) at org.apache.servicemix.jbi.framework.AutoDeploymentService$2.run(AutoDepl oymentService.java:592) at org.apache.geronimo.connector.work.WorkerContext.run(WorkerContext.java: 291) ... 2 more The same setup works just fine in JBoss. Has anyone come across this before? Regards, Grant McDonald
