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

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsbpel message

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


Subject: Issue - 267 - Fault for No Process Instance


This issue has been added to the wsbpel issue list with a status of "received". The status will be changed to "open" if a motion to open the issue is proposed and that motion is approved by the TC. A motion could also be proposed to close it without further consideration. Otherwise it will remain as "received".

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 - 267 - Fault for No Process Instance

Status: received
Date added: 14 Apr 2006
Date submitted: 12 April 2006
Submitter: Monica J Martin
Reference: Section 9.2, Declaring and Using Correlation Sets.

Update approved by the TC

If an inbound Web service request message arrives and both (1) no running process instance can be identified by a message correlation set mechanism and (2) all inbound message activities referencing the Web service operation have the createInstance attribute set to "no" are true then this scenario is out of scope of this specification because there is no process instance that would be able to handle it.

Description: In principle, it should be possible for WS-BPEL to require that a WSDL request-response operation defined in a portType associated with a myRole include a wsdl:fault element, which WS-BPEL could leverage to return runtime exceptions. Such a fault could occur at the level of the Web service representing the WS-BPEL process.

For the future, a fault should be considered to return runtime exceptions, that provide some notification back to the Web Service caller.

Other notes: This discussion occurred with Dieter Koenig, Ugo Corda, and I during the rewording of Section 9.2 during editors' reviews.
Submitter's proposal: Recognizing the state of the specification and the criticality of timing, open this issue and close with no change but mark as revisitable. It is recognized that some notification should go back to the Web Service caller. Runtime exceptions have not been defined for Web Services in general, and involves more changes to WS-BPEL specification than Section 9.2.
Changes: 14 Apr 2006 - new issue


To comment on this issue (including whether it should be accepted), please follow-up to this announcement on the wsbpel@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 - 267 - [anything]" or is a reply to such a message. If you want to formally propose a resolution to an open issue, please start the subject line "Issue - 267 - 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).



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