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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-transport message

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


Subject: RE: SOAP Proposal Documents


David,

The decision was made during discussions to move it back into the
SOAP-ENV:Fault element.  A careful reading of the specifcation says that the
<detail> element is intended for information related to the body.  However,
the spec also explicitly allows for extensions at  the SOAP-ENV:Fault child
level (i.e., a sibling of the <detail> element) without restriction on the
content of the error information.  Therefore, we were able to add an ebXML
namespace qualified element (the ErrorList) within the SOAP Fault element,
satisfying both goals of keeping the ebXML errors together and placing them
within the SOAP Fault element.

marc

==========================================================================
Marc Breissinger                                   voice (W): 703-460-2504
Director, Product Strategy - webMethods, Inc.	   voice (C): 703-989-7689
Email:  marcb@webmethods.com                               We're Hiring!!!
Email2: breissim@earthlink.net                   http://www.webMethods.com
==========================================================================





-----Original Message-----
From: David Fischer [mailto:david@drummondgroup.com]
Sent: Tuesday, February 20, 2001 6:48 PM
To: ebXML Transport (E-mail)
Subject: RE: SOAP Proposal Documents


Thanks Robert,

I originally had the ErrorList within SOAP-ENV:Fault and after discussions,
we decided to pull it out.  This was primarily due to the limitation on SOAP
Header errors.  We can put SOAP Body errors in SOAP Fault but there is a
limitation on SOAP Header errors... that requires another error list
external to SOAP Fault.   (see SOAP 1.1 section 4.4 sub-section "detail").

The discussion was to keep the ebXML errors together rather than
mix-and-match with two lists.  This limits the changes to our document.  We
would still support SOAP specific errors within SOAP Fault.

Did the discussion change afterwards to put it back?  I can certainly change
it back.  If it goes back, does there need to be another error list in the
Header?  IMO it was better (less work for the editors) to keep the errors
together.

Regards,

David Fischer
Drummond Group
817-371-8422

-----Original Message-----
From: Robert Fox [mailto:robertf@softshare.com]
Sent: Tuesday, February 20, 2001 4:39 PM
To: 'david@drummondgroup.com'; ebXML Transport (E-mail)
Subject: RE: SOAP Proposal Documents


1) The PPT diagram may need to be changed to show the eb:ErrorList element
inside the SOAP-FAULT as discussed

2) re: contribution credits in the document:

Robert Fox - Softshare

Thanx!

Great week gang!

~Rob

-----Original Message-----
From: David Fischer [mailto:david@drummondgroup.com]
Sent: Tuesday, February 20, 2001 2:31 PM
To: ebXML Transport (E-mail)
Subject: SOAP Proposal Documents


Welcome home from Vancouver,

These are the three SOAP related documents we used on the overhead in
Vancouver.  It is my understanding there is some problem with the ebXML/SOAP
press release scheduled for today.  It may not go out yet.  Please do not
distribute these documents too far.

On the PPT, the right picture is the old structure and the left is the new
proposed SOAP structure.

Also, Rik asked if any document contributor does not see their name on the
0.93 version, please reply with name and company so we may correct that
oversight.

Regards,

David Fischer
Drummond Group
817-371-8422



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

Search: Match: Sort by:
Words: | Help


Powered by eList eXpress LLC