RE: [bt-spec] New issue re: SOAP binding

[Peter Furniss <peter.furniss@choreology.com>]

The "soap-http-1" binding is explicitly to SOAP 1.1.

Anne is correct that the SOAPAction HTTP request header must be present with
SOAP 1.1.

When I drafted the text in the soap binding I neglected to check this
point - the intent, for actor-to-actor was that the  SOAPAction wasn't used.

Anne's solution would seem to be correct. (I see that soap 1.1 distinguishes
empty string  ("") from no value.)

SOAPAction is only an http request header.

I will make this a new issue. Since it is clearly a bug, and a solution is
ready, I will start it off at "solution proposed", rather than deferred.

Peter



> -----Original Message-----
> From: Tony Fletcher [mailto:tony_fletcher@btopenworld.com]
> Sent: 28 March 2002 01:19
> To: Furniss, Peter (Chor); bt-spec@lists.oasis-open.org; Anne Thomas
> Manes
> Subject: RE: [bt-spec] New issue re: SOAP binding
>
>
> Dear Anne, Peter and all other BTPers,
>
> I think we need to be a bit careful here as SOAP 1.2 seems to be
> making this
> parameter very definitely optional, if I read it correctly - see
> http://www.w3.org/TR/2001/WD-soap12-part2-20011217/#soapaction
>
> To quote:
> 'Some SOAP Receivers using this binding might need certain
> information to be
> readily available outside the message envelope. This binding uses an
> externalised expression of the SOAP Action feature to supply this
> information.
>
> Use of the SOAP Action feature is OPTIONAL. SOAP Receivers MAY use it as a
> hint to optimise processing, but SHOULD NOT require its presence
> in order to
> operate. Support for SOAPAction is OPTIONAL in implementations.
> Implementations SHOULD NOT generate or require SOAPAction UNLESS
> they have a
> particular purpose for doing so (e.g., a SOAP Receivers specifies
> its use).'
>
> This seems to be a significant change to the SOAP over HTTP binding as, as
> Anne points out correctly, SOAP 1.1 says that this header must be used (on
> the request - silent on response(?)) - see
> http://www.w3.org/TR/SOAP/#_Toc478383528
>
>
> Best Regards     Tony
> A M Fletcher
> Choreology Ltd., 13 Austin Friars, London EC2N 2JX     UK
> Tel: +44 (0) 20 76701787         Mobile: +44 (0) 7801 948219
> tony.fletcher@choreology.com <mailto:tony.fletcher@choreology.com>
> (Home: amfletcher@iee.org)
>
>
> -----Original Message-----
> From: Anne Thomas Manes [mailto:atm@systinet.com]
> Sent: 23 March 2002 18:48
> To: bt-spec@lists.oasis-open.org
> Subject: [bt-spec] New issue re: SOAP binding
>
>
> Based on 18 March 2002 revision 0.9.2.3.
>
> Lines 4937-4939 say:
>
> "The SOAPAction HTTP header shall be omitted when the SOAP message carries
> only BTP messages in the SOAP Body."
>
> In SOAP 1.1, the SOAPAction HTTP Header is required.
>
> I suggest the following instead:
>
> "The SOAPAction HTTP header shall contain no value when the SOAP message
> carries only BTP messages in the SOAP Body."
>
> Best regards,
>
> Anne Thomas Manes
> CTO, Systinet (formerly Idoox)
> www.systinet.com
>
>
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>
>