According to the standard WSDL descriptions that are part of the UDDI V2 standard, the SOAPAction is supposed to include a string that indicates the operation, e.g. "find_service". But individual implementations may override the SOAPAction parameter requirements.
Anne
At 12:47 PM 3/26/2004, you wrote:
What should be the value of the SOAPAction header attribute when sending a UDDI request.
I found that the registry http://www-3.ibm.com/services/uddi/inquiryapi will not work when i set an empty string for this header. The value need to be explict "" inorder for this to work. Other registries that i am connecting to are fine with the empty string. Why this difference? What is the standard?
e.g. in my Http client api, (1) setHeader("SOAPAction", ""); will not work only for the ibm registry (2) setHeader("SOAPAction", "\"\""); works
If he above explanation is not clear let me show you the tcp monitor trace: (1) If the headers are going like this, it will not work POST /services/uddi/inquiryapi HTTP/1.1 content-type: text/xml; charset=utf-8 soapaction: User-Agent: Jakarta Commons-HttpClient/2.0rc1 Host: www-3.ibm.com Content-Length: 268
(2) But the below one works POST /services/uddi/inquiryapi HTTP/1.1 content-type: text/xml; charset=utf-8 soapaction: "" User-Agent: Jakarta Commons-HttpClient/2.0rc1 Host: www-3.ibm.com Content-Length: 268
Thanks in Advance, dw
__________________________________ Do you Yahoo!? Yahoo! Finance Tax Center - File online. File on time. http://taxes.yahoo.com/filing.html
~~~~~~~~~~~~~~~~~~
Anne Thomas Manes
VP & Research Director
Burton Group
