wood burning stoves*
The moose likes Web Services and the fly likes Use of SoapAction Attribute ? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Web Services
Bookmark "Use of SoapAction Attribute ?" Watch "Use of SoapAction Attribute ?" New topic
Author

Use of SoapAction Attribute ?

yekkala krishna
Ranch Hand

Joined: Mar 04, 2007
Posts: 105
Hi,

In wsdl if we have operations more than one.Then its mandatory to use soapAction attribute under binding tag.

For example i am giving the below example:


<wsdl:binding name="GAT__InboxSoapBinding" type="s0:GAT__InboxPortType">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdlperation name="OpCreate">
<soapperation soapAction="urn:GAT__Inbox/OpCreate" style="document"/>
<wsdl:input>
<soap:header message="s0:ARAuthenticate" part="header" use="literal">
</soap:header>
<soap:body use="literal"/>
</wsdl:input>
<wsdlutput>
<soap:body use="literal"/>
</wsdlutput>
</wsdlperation>
<wsdlperation name="Monitor">
<soapperation soapAction="urn:GAT__Inbox/Monitor" style="document"/>
<wsdl:input>
<soap:header message="s0:ARAuthenticate" part="header" use="literal">
</soap:header>
<soap:body use="literal"/>
</wsdl:input>
<wsdlutput>
<soap:body use="literal"/>
</wsdlutput>
</wsdlperation>
</wsdl:binding>

With Regards,
Rama Krishna.Y
Peer Reynders
Bartender

Joined: Aug 19, 2005
Posts: 2922
    
    5
That shouldn't be the case. In the WSDL omitting the soapAction attribute is equivalent to setting soapAction="". It means that the SOAPAction HTTP header will be empty. The WS-I Basic Profile requires that a SOAP envelope inside an HTTP POST request is accompanied by an HTTP SOAPAction header - however it permits the SOAPAction header to be empty. The soapAction attribute simply specifies the content of the SOAPAction HTTP header. The content of the SOAPAction HTTP header is supposed to communicate the "intent" (e.g. operation) of the SOAP envelope, so that proxies and firewalls can act on it without looking into the XML SOAP envelope.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Use of SoapAction Attribute ?
 
Similar Threads
problem calling a remote webservice [ Algo Error]
Need Help regarding -- org.xml.sax.SAXException: Invalid element
MS Exchange web service: If the 'nillable' attribute is false in the schema, the 'xsi:nil' attribute
How to call update functionality from Java using web service
is it valid to have solicit and req-res in single portType ?