OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

security-services message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [security-services] Status or StatusCode as Top Level Element


Absolutely.  Good catch, and that is what we meant when we changed this section of text for V1.1

 

I'll make the edit.

 

Rob Philpott
RSA Security Inc.
The Most Trusted Name in e-Security
Tel: 781-515-7115
Mobile: 617-510-0893
Fax: 781-515-7020
mailto:rphilpott@rsasecurity.com

-----Original Message-----
From: Chopra, Dipak [mailto:dipak.chopra@sap.com]
Sent: Thursday, May 15, 2003 8:16 PM
To: security-services@lists.oasis-open.org
Subject: [security-services] Status or StatusCode as Top Level Element

 

In the error reporting section in SOAP Binding (Section 3.1.3.6, lines #314-318), it seems like the recommended way is to place <StatusCode> as the top level element in <Response> element within SOAP Body. I think this recommendation is not compliant with schema. Shouldn't we have <Status> (with <StatusCode> element) as the top level element in <Response>?

   

Dipak



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]