Paul Sandoz wrote:
> It is my understanding that the SOAP 1.2 HTTP binding does not use a
> SOAPAction HTTP header. Instead it is defined as a parameter on the
> MEDIA type [1]:
Ah, yes.
> "This optional parameter can be used to specify the URI that identifies
> the intent of the message. In SOAP 1.2, it serves a similar purpose as
> the SOAPAction HTTP header field did in SOAP 1.1. Namely, its value
> identifies the intent of the message.
>
> The value of the action parameter is an absolute URI-reference as
> defined by RFC 2396 [RFC 2396]. SOAP places no restrictions on the
> specificity of the URI or that it is resolvable."
>
>
> IIRC WS-I BP do requires that the SOAPAction HTTP header always be
> present and be quoted even if an empty string.
>
>
> So there are some different semantics depending on whether one is using
> SOAP 1.1 (when WS-I compliance is enabled) and SOAP 1.2.
I'll expand javadoc to cover this.
--
Kohsuke Kawaguchi
Sun Microsystems kohsuke.kawaguchi_at_sun.com