Develop a good habit recording solution at any time a good memory as bad written, previously deployed in the WebSphere axis2 had spent the night and today the decision was made to write the record in this
WebSphere6 + axis2 1.3
Released when webservice service the following exception occurs
java.lang.NoSuchMethodError: javax/wsdl/Operation.getExtensibilityElements()Ljava/util/List; at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateOperations(WSDL11ToAxisServiceBuilder.java:1010) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populatePortType(WSDL11ToAxisServiceBuilder.java:399) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateEndpoints(WSDL11ToAxisServiceBuilder.java:318) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService(WSDL11ToAxisServiceBuilder.java:288) at ...
Apache Muse - Conflicting Version of WSDL4J in WebSphere Deployments
When deploying your Muse-based applications on IBM WebSphere Application Server (WAS) 6.0 or 6.1, you need to be aware that Muse relies on WSDL4J 1.6.1 while the server's core libraries include WSDL4J 1.4. If you install your application using the default class loading system, it will fail to start because the Muse framework depends on WSDL4J APIs that are only available in WSDL4J 1.5 and above. To work around this issue, you can configure the server to use the application's class loader before the container or system class loaders ; this will ensure that the WSDL4J classes that are in your application's / WEB-INF/lib directory will be loaded before those in $ WAS_HOME / lib.
If you are developing and deploying your application through IBM Rational Application Developer (RAD), you can make the required changes by setting the class loader mode to PARENT_LAST and the class loader policy to SINGLE.
If you are installing your application through the WAS admin console, select Enterprise Applications> Your Application> Class loading and update detection. You should then check the boxes labeled as follows:
* Classes loaded with application class loader first
* Single class loader for application
Making these changes should not affect your other (non-Muse) applications because, having no WSDL4J JAR files of their own, the server will continue up the chain of class loaders until the container's class loader discovers WSDL4J 1.4 in $ WAS_HOME / lib.
Is the first application of its own class library loading the last parent without loading the wsdl class that comes with WebSphere
2, change the label after the struts can not resolve anything thrown at this time of the application to delete this time inside the servlet.jar that comes with WebSphere
3, then this exception when thrown
RAD 6.0.1, DataSource ClassCastException
delete this jar package jdbc2_0-stdext.jar (hibernate zone), you can check this under the DataSource class in which the package are deleted useless
4 restart successfully posted ok