[SOAPAction] Error: Unable to determine operation id

To try to make it easier for those who google with error message, here are two possible explanations for this error message, when using JAX-RPC based Web Service runtine.
a) The value of the SOAPAction attribute on the HTTP Header on the wire do not match with the value expected by the service endpoint, as advertised on the WSDL soap:binding.
Wire sample:
...
User-Agent: Oracle HTTPClient Version 10h
SOAPAction: "CalculatePrice"
...

WSDL snippet:
44    <binding name="XmlCalculatePricePort" type="tns:XmlCalculatePricePort">
45      <soap:binding transport="http://schemas.xmlsoap.org/soap/http"
46                    style="document"/>
47      <operation name="CalculatePrice">
48        <soap:operation soapAction="CalculatePrice"/>
49        <input>
50          <soap:body use="literal"/>
51        </input>
52        <output>
53          <soap:body use="literal"/>
54        </output>
55      </operation>
56    </binding>


Note: the use of the quote is highly recommended for better interoperability.

b) If the service do not rely on this HTTP header to route incomming messages to specific operation (uses empty value in the WSDL soap:binding), it will use the fully qualified name (or QName) of the first child of the soap:body element to route the incomming message -- {http://siebel.com/OrderManagement/Quote/PSP}CalculatePrice_Input in the example below. If the value on the wire does not match with the one expected (and advertized in the WSDL), you may get the error message listed above. In such case, make sure that the name is properly qualified. A common mistake here is to use the wrong namespace.

  1  <?xml version = '1.0' encoding = 'UTF-8'?>
  2  <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
  3                xmlns:xsd="http://www.w3.org/2001/XMLSchema"
  4                xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  5                xmlns:ns0="http://siebel.com/OrderManagement/Quote/PSP">
  6     <env:Body>
  7        <ns0:CalculatePrice_Input>
  8           <ListOfQuote xmlns="http://siebel.com/OrderManagement/Quote/Data">
  9              <Quote>

Comments

Post a Comment

Popular posts from this blog

Changing the version of JDK used by JDeveloper

I have recently learned a quick and lazy way to change the version of the JDK used to run JDeveloper 10g R3. I am sure there is an option somewhere in the configuration screen to do the same, which I couldn't find... While JDeveloper is not running, locate the embedded JDK on disk and rename (or delete) that directory. For me, it was C:\opt\jdev\jdk. Once it's done, restart and you will by asked to locate the version of the JDK you want to use. It's another step to get going with JAVA on Vista. -ecco
Read more

Connection reset from a WCF Web Service

Here is an error message you may see, when calling WCF Web Services from java: IOException retrieving the response: java.net.SocketException: Connection reset As it may not be obvious the first time you see it, this may save you some time. One reason for this behaviour is when the WCF endpint is expecting to see wsa:Action SOAP header in the request. To find out if you are facing this case, you have to look inside the WSDL, and search for the policy that describes the contract for your endpoint. <wsp:Policy wsu:Id="CustomBinding_Echo1_policy">   <wsp:ExactlyOne>     <wsp:All>       <wsaw:UsingAddressing/>     </wsp:All>   </wsp:ExactlyOne> </wsp:Policy> To make this a concrete example, here is a sample WSDL . To find the policy, you will need to follow the import as the policy are not always advertized in the top-level document. Here is how the import looks:   <wsdl:import namespace="http://example.org/" location="h
Read more

unexpected null value for literal data

There is a challenge that is hard to overcome at first; making sense of error messages. You can always Google with the text of the error, “unexpected null value for literal data” and hope to be lucky . If you are using Oracle Application Server 10.1.3.0, here is the explaination for the message and two ways out. The Exception: unexpected null value for literal data at oracle.j2ee.ws.common.util.exception.JAXRPCExceptionBase.<init>(JAXRPCExceptionBase.java:52) at oracle.j2ee.ws.common.encoding.SerializationException.<init>(SerializationException.java:26) ... The relevant schema: <complexType name="Customer"> <sequence> <element name="address" type="tns:Address"/> <element name="firstName" type="string"/> <element name="lastName" type="string"/> </sequence> </complexType> A sample code that will cause this exception: public void testServ() throw
Read more