I worked on such a case, and I had some issues in hitting the Composite Service. Once the project has been developed and deployed, you can use any web service testing tool to test it. I used SoapUI in this case. I imported the WSDL, created a request and hit the web service using the option of "callFunctionStateless" (the SoapUI created two methods - callFunctionStateless and callFunctionStateful). I got an error as below:
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header/>
<env:Body>
<env:Fault xmlns:fpre="http://xmlns.oracle.com/bpel/rules">
<faultcode>fpre:operationErroredFault</faultcode>
<faultstring/>
<faultactor/>
<detail>
<errorInfo xmlns="http://xmlns.oracle.com/bpel/rules">
<errorMessage>RulesWithoutBPEL</errorMessage>
</errorInfo>
</detail>
</env:Fault>
</env:Body>
</env:Envelope>
<env:Header/>
<env:Body>
<env:Fault xmlns:fpre="http://xmlns.oracle.com/bpel/rules">
<faultcode>fpre:operationErroredFault</faultcode>
<faultstring/>
<faultactor/>
<detail>
<errorInfo xmlns="http://xmlns.oracle.com/bpel/rules">
<errorMessage>RulesWithoutBPEL</errorMessage>
</errorInfo>
</detail>
</env:Fault>
</env:Body>
</env:Envelope>
I then realized that under the soap:Body, there is a method by name <orac:callFunctionStateless name="">. In the attribute, the name of the decision service which has been exposed as web service should be given. It worked after that !
Peace!
Cheers,
-AR
No comments:
Post a Comment