Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

is soapAction attribute required in WSDL definition file to be valid WS-I Basic

 
Slava Lovkiy
Greenhorn
Posts: 29
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi, I have question about 'soapAction' attribute in soap binding declaration in WSDL file.
According to WSDL spec http://www.w3.org/TR/wsdl, section 3.4, soap peration sais:
The soapAction attribute specifies the value of the SOAPAction header for this operation. This URI value should be used directly as the value for the SOAPAction header; no attempt should be made to make a relative URI value absolute when making the request. For the HTTP protocol binding of SOAP, this is value required (it has no default value).


While in WS-I Basic profile, seciont 4.3.4 SOAPAction Header Syntax with have the following correct example:


So, according to WSDL specification, soapAction attribute for soap peration element is required and does not have default vaule, while it could be omitted according to WS-I Basic profile.
Is there any contradictions between WSDL spec. and WS-I Basic profile, or I�m missing something?
 
Raju Sri
Ranch Hand
Posts: 108
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Slava,

We should follow as per WS-I Basic profile at least for exam point of view. For example as per WSDL we can use HTTP,SMTP and FTP protocols but WS-I Basic profile restrict to only HTTP.So we no need to worry about the WSDL conflicts with WS-I basic profile.We will always follow as per WS-I Basic Profile 1.0.

So soapAction is not required and we can omit it.

Please correct me If I am wrong.

Regards
Raju
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic