| From | Sent On | Attachments |
|---|---|---|
| ws-bpel issues list editor | Jul 14, 2004 7:55 pm |
| Subject: | Issue - 141 - Standard Fault Format | |
|---|---|---|
| From: | ws-bpel issues list editor (pete...@choreology.com) | |
| Date: | Jul 14, 2004 7:55:27 pm | |
| List: | org.oasis-open.lists.wsbpel | |
This issue has been added to the wsbpel issue list. The issues list is posted as a Technical Committee document to the OASIS WSBPEL TC pages on a regular basis. The current edition, as a TC document, is the most recent version of the document entitled in the "Issues" folder of the WSBPEL TC document list - the next posting as a TC document will include this issue. The list editor's working copy, which will normally include an issue when it is announced, is available at this constant URL.
Issue - 141 - Standard Fault Format
Status: open Categories: Fault handling Date added: 15 Jul 2004 Submitter: Yaron Y. Goland Date submitted: 15 July 2004 Description: When we specify BPEL faults it would be goodness if implementations had a standard, portable, way of specifying platform specific data inside of the fault. Submitter's proposal: We should introduce a standard fault format to be used with BPEL faults. All BPEL generated faults would be defined to have bodies and those bodies would have some kind of extensible internal structure. This would have no affect on WSDL generated faults (e.g. SOAP faults). This is really a best practice. Changes: 15 Jul 2004 - new issue
------------------------------------------------------------------------------
To comment on this issue, please follow-up to this announcement on the wsb...@lists.oasis-open.org list (replying to this message should automatically send your message to that list), or ensure the subject line as you send it starts "Issue - 141 - [anything]" or is a reply to such a message. If you want to formally propose a resolution, please start the subject line "Issue - 141 - Proposed resolution", without any Re: or similar.
To add a new issue, see the issues procedures document (but the address for new issue submission is the sender of this announcement).





