Last post Dec 08, 2014 02:19 AM by ramana123
Dec 02, 2014 06:41 AM|ramana123|LINK
I have WCF service which requires a SOAP Header to be passed in order to be processed consumers request properly. But wehn we publish WSDL to consumers it doest have any soAP Headere requirements as it general like Operation and paramters information.
The SErvice exepcts a SOAP header as it look for these headers in Message Inspectors to authorse the call.
WHen we give WSDL to the users its plain WSDL it doesnt sate anyting about Header requirement. So, in genral do we need to specify the Header requirements to the comsumers in WSDL? (offsourse will tell them in offline this) if so then how to add this headers
info in WSDL so that conumers know WCF expects headers?
Dec 05, 2014 09:46 AM|Shawn - MSFT|LINK
The optional SOAP Header element contains application-specific information (like authentication, payment, etc) about the SOAP message. The attributes defined in the SOAP Header defines how a recipient should process the SOAP message.
The SOAP mustUnderstand attribute can be used to indicate whether a header entry is mandatory or optional for the recipient to process.
If you add mustUnderstand="1" to a child element of the Header element it indicates that the receiver processing the Header must recognize the element. If the receiver does not recognize the element it will fail when processing the Header.
For more information, you could refer to:
Dec 08, 2014 02:19 AM|ramana123|LINK
Hi Shawn, I am not quite get it; I need to know how to enable or modify the WSDL on server side when publishing to enable header information in it. I am not sure if one can do that with MustUInderstand attribute. if so where I should do that?