I know this is coming a bit late, but I am having the same issue now. Well this plus another one. The problem with JavaClassNotFound in my case was caused by the capability being compiled in JDK1.5 and WebSphere 6.0 is using JDK1.4. The error in WebSphere is misleading as it should through a compatibility exception I think.
The other issue I am having is that when the deployer is set to use parent last - which should be the same as use Application class loader first (I am using it under ND so the menus look different I think) the Axis-2 endpoint does not get deployed due to an exception related to commons-logging: Caused by java.lang.ClassCastException: The application has specified that a custom LogFactory implementation should be used but Class 'com.ibm.ws.commons.logging.TrLogFactory' cannot be converted to 'org.apache.commons.logging.LogFactory' This seems to be due to the fact that WAS6.0 has it's own implementation of commons-logging which is outside of my application classloader. If I use parent first this problem does not show but I have the WsdlUtils error. So I am trying to upgrade my small cluster to WAS6.1. marco_parmiani wrote: > > Just a quick note to specify the exception returned by the server: > java.lang.RuntimeException: [ID = 'JavaClassNotFound'] The Java class > specified was not found: com.example.wsdm.donnafugata.MyCapability. Make > sure the correct .class or .jar file is in the classpath. > > The problem is that the jar is included in the war file (and the war file > is the same on 6.0 and 6.1), but on 6.0 the module just won't run. It > seems a classloading problem again. > > Have someone tried to deploy a muse war on a 6.0 Websphere? > Thanks again > Marco > -- View this message in context: http://www.nabble.com/Deploying-on-Websphere-6.0-tf3674297.html#a10627712 Sent from the Muse User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
