SoapAction in WSDL

[Former Member]

Sometimes the soapAction part would not appear in a legal wsdl. For instance:

<wsdl:binding name="T_MaterialMasterBinding" type="hrmsap:T_MaterialMasterInterface">

<wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>

<wsdl:operation name="process">

<wsdlsoap:operation/>

<wsdl:input>

<wsdlsoap:body use="literal"/>

</wsdl:input>

</wsdl:operation>

</wsdl:binding>

In this case, what should I configure as the "Soap Action" in soap receiver adapter?

Thanks and B'Rgds

[bhavesh_kantilal · Accepted solution]

SOAP action is not a mandatroy field in the receievr SOAP adapter.

If the Webservice does not expect a SOAP action you can leave the field blank in the SOAP adapter.

Regards

bhavesh

[Former Member · Accepted solution]

After send the soap to the wsdl, we received the following reply message:

<faultstring>

Operation Not found EPR is http://172.25.99.83:8080/axis2/services/T_ErrorMessagePOLService and WSA Action = </faultstring>

I think it comes by the missing of soap action part.

Do you know how to solve it?

[Former Member · Accepted solution]

HI,

Yes some times may not require i too heard,but in what type of situations , can you please explain.

regarding SOAP Action

Specify the SOAP action. The action specifies the value for the SOAPAction in Web service messages; set the indicator.

we can have in messahe header also ..SOAP Action : THeaderSOAPACTION

http://help.sap.com/saphelp_nw2004s/helpdata/en/29/5bd93f130f9215e10000000a155106/content.htm

Regards

Chilla

[bhavesh_kantilal · Accepted solution]

I dont know in what situations but in one of our implementations when we were integrating with a 3rd party vendore providing webservices the WSDL enevr contained any SOAP actions.

Regards

Bhavesh

[Former Member · Accepted solution]

Solved by myself by use the operstion name.

[henrique_pinto · Accepted solution]

If the operation is the expected soap action (as it should be in a well-created wsdl), it should explicitely say so in the wsdl file.

It was badly created.

Regards,

Henrique.