RE: SOAP Proposal Documents

[Marc Breissinger <marcb@webmethods.com>]

Dick,

some comments...

<snip>
- no support for enumerated listing of errors within a SOAP-ENV:Fault
</snip>

As previously stated, a careful reading of the specifcation says that the
<detail> sub-element is intended for information related only to SOAP Body
error.  However, the spec also explicitly allows for extensions at the
SOAP-ENV:Fault sub-element 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.

<snip>
- Use of HTTP 500
</snip>

Use of HTTP 500 in the error process is specific to the SOAP HTTP Binding
and seems reasonable when an HTTP transport is used.  I don't understand how
this is a problem.  The bining states that:

In case of a SOAP error while processing the request, the SOAP HTTP server
MUST issue an HTTP 500 "Internal Server Error" response and include a SOAP
message in the response containing a SOAP Fault element (see section 4.4)
indicating the SOAP processing error.

In other words, if the SOAP processor (in our case, the envelope processor)
has an error, it must return in the HTTP response.  It should never get to
the ebXML processor to have any other kind of error, so why do we care?  I
would think we would just follow the SOAP HTTP binding in that case.

<snip>
- Reporting Header errors
</snip>

see comments above re:extensions being unrestricted in content

IMHO, I would prefer to see all errors kept together and within the SOAP
framework.

marc

-----Original Message-----
From: Dick Brooks [mailto:dick@8760.com]
Sent: Wednesday, February 21, 2001 8:22 AM
To: david@drummondgroup.com; ebXML Transport (E-mail)
Subject: RE: SOAP Proposal Documents


I agree with David. I seem to recall a couple of issues from our discussion
of this:
- no support for enumerated listing of errors within a SOAP-ENV:Fault
- Use of HTTP 500
- Reporting Header errors

Keeping the ErrorList within the SOAP-ENV:Body offers us more flexibility,
IMO.

Dick Brooks
http://www.8760.com/


-----Original Message-----
From: David Fischer [mailto:david@drummondgroup.com]
Sent: Tuesday, February 20, 2001 5: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


------------------------------------------------------------------
To unsubscribe from this elist send a message with the single word
"unsubscribe" in the body to: ebxml-transport-request@lists.ebxml.org