RE: [wss] Updated Interop Scenarios (with updated TOC) - wss-interop1-draft-05.doc

[Christopher B Ferris <chrisfer@us.ibm.com>]

<decloak>
I would point out that the WS-I Basic Profile 1.0[1] requires SOAPAction 
HTTP header 
field to be present with a quoted empty string if there is no value for 
SOAPAction. Given the large number
of vendors who have pledged support for the BP1.0, it might be a good idea 
to base any
interop scenarios that build on SOAP1.1 and WSDL 1.1 on the WS-I Basic 
Profile 1.0 as a 
foundation.

Just a suggestion;)

[1] http://ws-i.org/profiles/basic/2003-03/basicprofile-1.0-bdad.html

</decloak>

Cheers,

Christopher Ferris
STSM, Emerging e-business Industry Architecture
email: chrisfer@us.ibm.com
phone: +1 508 234 3624

"Chris Kaler" <ckaler@microsoft.com> wrote on 06/02/2003 03:31:59 PM:

> I don't understand why we require SOAPaction not to be present.  It
> should be ignored if not understood like other HTTP headers.
> 
> -----Original Message-----
> From: Hal Lockhart [mailto:hlockhar@bea.com] 
> Sent: Friday, May 30, 2003 2:03 PM
> To: wss@lists.oasis-open.org
> Subject: [wss] Updated Interop Scenarios (with updated TOC) -
> wss-interop1-draft-05.doc
> 
> Sorry, forgot to update the TOC.
> 
> Hal
> 
> You may leave a Technical Committee at any time by visiting 
http://www.oasis-open.
> org/apps/org/workgroup/wss/members/leave_workgroup.php
>