Binding Fault invoking an axis2 webService from BPEL

Question

Hi,
I have deployed axis2 on the OC4J application server. And then I have deployed a web service to axis2. I can access the wsdl and create the partner link in the jdeveloper. The problem appears in execution time.
When I run the BPEL process the following error appears:
<2008-08-27 14:41:20,906> <DEBUG> <default.collaxa.cube.ws> <WSIFInvocationHandler::invoke> invoke failed
org.collaxa.thirdparty.apache.wsif.WSIFException: [email protected]2 : Could not find binding output for operation insertOrUpdate at com.collaxa.cube.ws.wsif.providers.http.WSIFOperation_HTTP.getOutputMIMEXmlPart(WSIFOperation_HTTP.java:205) at com.collaxa.cube.ws.wsif.providers.http.WSIFOperation_HTTP.executeRequestResponseOperation(WSIFOperation_HTTP.java:308)
     at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:435)
From .NET application we can invoke the web service so I think the web service is ok. Does anybody know how to solve this issue? I have been searching for a solution and I have only found questions about this..
Any help would be appreciated.
Thanks in advance,
Zaloa

Answer 1

Hi,
Just in case someone runs into the same problem, I live here my solution:
In may case the problem was the wsdl definition. I developed the web service in java and generated the wsdl with Maven. Automatically it generates the wsdl like this (I just copy the last section):
<wsdl:service name="tso-ws">
<wsdl:port name="tso-wsHttpSoap11Endpoint" binding="ns:tso-wsSoap11Binding">
<soap:address location="http://localhost:8080/axis2/services/tso-ws"/>
</wsdl:port>
<wsdl:port name="tso-wsHttpSoap12Endpoint" binding="ns:tso-wsSoap12Binding">
<soap12:address location="http://localhost:8080/axis2/services/tso-ws"/>
</wsdl:port>
<wsdl:port name="tso-wsHttpEndpoint" binding="ns:tso-wsHttpBinding">
<http:address location="http://localhost:8080/axis2/services/tso-ws"/>
</wsdl:port>
</wsdl:service>
The problem was the <wsdl:service name="tso-ws"> section. There were 3 port definitions with 3 different bindings but all of them have the same service location. So In the BPEL process I created the partner link using the service location.
I guess BPEL was using the http binding, so I deleted two of the por definitions and just left this in the <wsdl:service name="tso-ws"> section of the wsdl
<wsdl:service name="tso-ws">
<wsdl:port name="tso-wsHttpSoap12Endpoint" binding="ns:tso-wsSoap12Binding">
<soap12:address location="http://localhost:8080/axis2/services/tso-ws"/>
</wsdl:port>
By doing this, it works. I read in some forums that BPEL doesn't work with the http_post protocol so that's why I deleted that definition. And someone told me that it uses soap12 so that's why I deleted that definition also.
That's the way I solved it. Hope this helps.
Regards,
Zaloa