Hello Robert,
Your comment sounds like your saying that an empty soap action ("") is
not valid for RPC/literal and DOC/literal. That's not what you mean, is it?
The WS-I BP1.0 spec uses an empty soapAction in its examples to denote a
correct, interoperable value. The WS-I BP1.0 applies to WSDLs of style
RPC/literal and DOC/literal.
CORRECT:
A WSDL Description that has:
<soapbind:operation />
or
<soapbind:operation soapAction="" />
results in a message with a corresponding SOAPAction HTTP header field
as follows:
SOAPAction: ""
As far as I know, Axis's stubs will set the SOAPAction header to
whatever is defined in the corresponding soapAction attribute in the
WSDL, and the server will complain when it is not set ("" is fine, but
nothing is a no-no).
Regards,
Dies
robert wrote:
Sure, soap action can be "" . However, that typically is only valid for a wsdl
using RPC encoded style. I've never seen Doc / lit wsdl without a soap
action.
HTH,
Robert
http://www.braziloutsource.com/
Em Quarta 19 Abril 2006 15:08, o [EMAIL PROTECTED] escreveu:
Can you configure axis to default the SOAPAction as being ""? I have a
client which is sending me a message without the SOAPAction header.
