Topic
  • No replies
ar54906
ar54906
5 Posts

Pinned topic Application could not be started - After Installation in esb server

‏2013-03-20T14:54:06Z |
Hi,
My Mediation module was working fine. Recently i did a wsdl change and again redeployed my module. I also regenerated the binding(in export) and deployed.

But the Problem is, am unable to start the application.

1) From logs i came to know, the old wsdl generated during Export binding creation still been referred within the server somewhere...

But its working fine in my local machine...

What i did is, i took the old autpo generated wsdl, pointed the existing export to the old wsdl and made the application to start.

But i know this is a temporary work around...

Good solution is solicited.
The following error is thrown for this reason:

3/20/13 10:06:58:877 CET 0000004d WSDL11ToAxisS E org.apache.axis2.description.WSDL11ToAxisServiceBuilder populateService org.apache.axis2.AxisFault: Service {http://asasas.com/myService/V04R01//Binding2}myservice_myServiceHttpService was not found in the WSDL
3/20/13 10:06:58:891 CET 0000004d WASAxis2MetaD E WSWS7045E: The ConfigurationContext for the myWeb.war application module cannot be created correctly because of the following error: java.lang.ClassCastException: com.ibm.wsdl.ServiceImpl incompatible with javax.xml.ws.Service
3/20/13 10:06:58:896 CET 0000004d WASAxis2Compo E WSWS7007E: The myWeb.war application module cannot be loaded correctly because of the following error: java.lang.ClassCastException: com.ibm.wsdl.ServiceImpl incompatible with javax.xml.ws.Service