jvm - java.lang.NoClassDefFoundError: org.apache.woden.resolver.URIResolver -
getting below exception after deploying application in was8. using axis2 1.7.4 family woden api , impl 1.0m8. please help
java.lang.noclassdeffounderror: org.apache.woden.resolver.uriresolvergetting @ java.lang.j9vminternals.verifyimpl(native method) @ java.lang.j9vminternals.verify(j9vminternals.java:93) @ java.lang.j9vminternals.initialize(j9vminternals.java:170) @ org.apache.axis2.deployment.moduledeployer.deploy(moduledeployer.java:65) @ org.apache.axis2.deployment.repository.util.deploymentfiledata.deploy(deploymentfiledata.java:136) @ org.apache.axis2.deployment.deploymentengine.dodeploy(deploymentengine.java:815) @ org.apache.axis2.deployment.repositorylistener.loadclasspathmodules(repositorylistener.java:222) @ org.apache.axis2.deployment.repositorylistener.init2(repositorylistener.java:71) @ org.apache.axis2.deployment.repositorylistener.<init>(repositorylistener.java:64) @ org.apache.axis2.deployment.deploymentengine.loadfromclasspath(deploymentengine.java:177) @ org.apache.axis2.deployment.filesystemconfigurator.getaxisconfiguration(filesystemconfigurator.java:135) @ org.apache.axis2.context.configurationcontextfactory.createconfigurationcontext(configurationcontextfactory.java:64) @ org.apache.axis2.context.configurationcontextfactory.createconfigurationcontextfromfilesystem(configurationcontextfactory.java:210) @ org.apache.axis2.client.serviceclient.configureserviceclient(serviceclient.java:151) @ org.apache.axis2.client.serviceclient.<init>(serviceclient.java:144)
and later below getting classnotfoundexception also
caused by: java.lang.classnotfoundexception: org.apache.woden.resolver.uriresolver @ org.eclipse.osgi.internal.loader.bundleloader.findclassinternal(bundleloader.java:506) @ org.eclipse.osgi.internal.loader.bundleloader.findclass(bundleloader.java:422) @ org.eclipse.osgi.internal.loader.bundleloader.findclass(bundleloader.java:410) @ org.eclipse.osgi.internal.baseadaptor.defaultclassloader.loadclass(defaultclassloader.java:107) @ java.lang.classloader.loadclass(classloader.java:650) ... 27 more
if you're going bring own web services implementation, have run parent_last class loading (or, preferably, package version of web services implementation in shared library isolated class loader) , disable built-in web services engine in websphere. based on exception stack, appears happening in web services engine interacting websphere's version , triggering load dependency websphere doesn't package. setting environment use version resolve that.
note websphere includes axis2, unless strictly dependent on specific point release, there's chance best solution rely on websphere's web services provider, rather bringing own. simplify configuration, since won't need mess class loading delegation settings or system properties disabling web services provider.
Comments
Post a Comment