-
-
Notifications
You must be signed in to change notification settings - Fork 3
SoapActionComplement: because sometimes it's necessary even more!
Cussa Mitre edited this page Feb 7, 2018
·
1 revision
A user reported to us that on his webService, the call needs to have more one information on the SOAPAction header. On the old implementation, the SOAPAction was generated based on the Namespace + method name. But, as it was not enough, we create a possibility to go further!
Now, when call the method Invoke, you can pass more one parameter, the SoapActionComplement. This parameter will be inserted on the SOAPAction header. See the example below:
var wsCon = new WebService("http://localhost/XitSoap/ProductService.asmx", "http://schemas.hodstudio.com/HodStudio.Services.ProductService/2.0");
wsCon.AddParameter("Name", "product 01");
var result = wsCon.Invoke<Product>("SearchProduct", "IProductService");
SOAPAction: "http://schemas.hodstudio.com/HodStudio.Services.ProductService/2.0/IProductService/SearchProduct" namespace/SoapActionComplement/methodName
This was a request by the user maracuja-juice on Create new parameter SoapActionComplement.
- Home
- Migrating from v1 to v2
- Referencing the Library
- Make a simple call
- Adding Parameters
- Adding Authentication
- Adding Custom Headers
- Calling a web method without use a typed return
- Using the WsContract and the ServiceCatalog
- Using the WsContract just to use the namespace
- Using the WsMapper: no more ugly properties!
- SoapActionComplement: because sometimes it's necessary even more!