NEW ISSUE: WS-BA: Permit Fault as response to Close

[Alastair Green <alastair.green@choreology.com>]

Issue name -- WS-BA: Permit Fault as response to Close
 
PLEASE DO NOT REPLY TO THIS EMAIL OR START A DISCUSSISON THREAD UNTIL 
THE ISSUE IS
ASSIGNED A NUMBER.
 
The issues coordinator will notify the list when that has occurred.
 
Target document and draft:
 
Protocol:  WS-BA
 
Artifact:  spec
 
Draft:  BA spec cd 2
 
Link to the document referenced:
 
http://www.oasis-open.org/committees/download.php/18819/wstx-wsba-1.1-spec-cd-02.doc
 
Section and PDF line number:  section , lines
 

Issue type:  Design
 

Related issues:
 
 
Issue Description:
 
At present it is not possible to send Fault in response to Close. (It is 
possible to send Fault in response to Compensate.) Model requirements 
such as "quote-to-order" and tentative operations cannot be supported 
without ability to fault closure.

 
Issue Details

There are many examples of scenarios where completion of an activity 
involves additional application work in a participant, just as 
cancellation requires compensatory work. The model section of the spec 
refers to the following iconic case:

" Allow a business application to select which child tasks are included 
in the overall outcome processing.  For example, a business application 
might solicit an estimate from a number of suppliers and choose a quote 
or bid based on lowest-cost."

A natural application of WS-BA in this scenario is:

Buy-side sends Request For Quote (RFQ) with BA context to sell-side.
Sell-side sends Completed ("prepared") to coordinator, and responds with 
Quote to  buy-side. Quote is  "firm": it will be honoured if quote 
becomes order.
Buy-side likes quote and wants to execute order, so sends Close (no need 
to send application Order message).

As with compensations, the "react to Close" application operation 
effectively invoked by sending Close is capable of failing (business 
exceptions will be raised). The most likely reason here is that the 
quote has timed-out.

A failure of this kind should be signalled in response to the Close message.

Any scenario where participants move through application states 
"Pending" to "Final" requires this feature.


Proposed resolution
 
Please see the document uploaded in November for the changes required 
for Participant completion:

http://www.oasis-open.org/committees/download.php/15696/2005-12-01.WS-BA.1.0.PC.input.state.tables.Fault-on-Close.change.xls

The version of the state table in the uploaded document has the old 
orientation of states and messages, but the point still stands.