Make sure that you have the appropriate wsdl4j jar on your application's
classpath. If you do, you will probably need to do more research to see where
the conflicting jar is coming from. I think WebSphere provides the ability to
dump the classloader but I can't remember how to do it.
Below is the output from jarfinder.com. One of these jars (probably an
axis-related one), is the one you need.
javax.wsdl.PortType
known versions
1. abstract interface javax.wsdl.PortType [581 bytes, jvm >= 1.2 ]
* wsdl4j.jar
2. abstract interface javax.wsdl.PortType [667 bytes, jvm >= 1.4 ]
* wsdl4j.jar
* jbossall-client.jar
3. abstract interface javax.wsdl.PortType [630 bytes, jvm >= 1.2 ]
* wsdl4j-1.5.1.jar
* wsdl4j.jar
* axis-wsdl4j-1.2.1.jar
* axis-wsdl4j-1.3.jar
* axis-wsdl4j-1.2.jar
* axis-wsdl4j-1.5.1.jar
* client.jar
* dspace-lni-client-1.5.0-rc1-jar-with-dependencies.jar
* dspace-lni-client-1.5.0-jar-with-dependencies.jar
* dspace-lni-client-1.5.0-beta2-jar-with-dependencies.jar
* dspace-lni-client-1.5.1-beta-jar-with-dependencies.jar
* dspace-lni-client-1.5.1-jar-with-dependencies.jar
* wsdl4j-1.5.3.jar
* wsdl4j-1.5.2.jar
4. abstract interface javax.wsdl.PortType [488 bytes, jvm >= 1.2 ]
* org.apache.servicemix.bundles.wsdl4j-1.6.1-4.0-m1.jar
* org.apache.servicemix.bundles.wsdl4j-1.6.1_1.jar
* javaee-api-5.0.4.jar
* javaee-api-5.0.5.jar
* javaee-api-5.0.2.jar
* javaee-api-5.0.1.jar
* javaee-api-5.0.0.jar
* javaee-api-5.0.3.jar
* javaee-api-5.1.0-M1.jar
* wsdl4j-1.6.1.jar
* wsdl4j-1.6.2.jar
5. abstract interface javax.wsdl.PortType [667 bytes, jvm >= 1.2 ]
* axis-wsdl4j-1.2-RC3.jar
6. abstract interface javax.wsdl.PortType [637 bytes, jvm >= 1.1 ]
* axis-wsdl4j-1.2-beta-3.jar
* axis-wsdl4j-1.2-RC1.jar
* axis-wsdl4j-1.2-beta-2.jar
* axis-wsdl4j-1.2-RC2.jar
7. abstract interface javax.wsdl.PortType [630 bytes, jvm >= 1.2 ]
* groovysoap-all-jsr06-0.1.jar
8. abstract interface javax.wsdl.PortType [588 bytes, jvm >= 1.1 ]
* wsdl4j-1.4.jar
* wsdl4j-1.0.jar
-----Original Message-----
From: Alexander Rosemann [mailto:[email protected]]
Sent: Friday, August 20, 2010 9:18 AM
To: [email protected]
Subject: WebSphere 6.1, axis2 1.4.1 and java.lang.NoSuchMethodError
I try to get an application running in websphere 6.1. The application
has axis2 1.4.1 embedded. I set the classloader to "parent last" to make
sure the application loads its classes first.
When I go to http://localhost:9080/myapp/services/listServices it tells
me that there are faulty services. When clicking on the link (shwing the
full path to the faulty aar) I get the following stack trace:
Error: java.lang.NoSuchMethodError:
javax/wsdl/PortType.getExtensionAttributes()Ljava/util/Map; at
org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populatePortType(WSDL11ToAxisServiceBuilder.java:572)
at
org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateEndpoints(WSDL11ToAxisServiceBuilder.java:469)
at
org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService(WSDL11ToAxisServiceBuilder.java:363)
at
org.apache.axis2.description.WSDL11ToAllAxisServicesBuilder.populateAllServices(WSDL11ToAllAxisServicesBuilder.java:107)
at ...
An interesting fact is, deploying the standalone axis2.war works like a
charm. Any idea what I can try to get it working?
Cheers,
Alex
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
STATEMENT OF CONFIDENTIALITY:
The information contained in this electronic message and any attachments to
this message are intended for the exclusive use of the addressee(s) and may
contain confidential or privileged information. If you are not the intended
recipient, please notify WHI Solutions immediately at [email protected],
and destroy all copies of this message and any attachments.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
