WS-AT: Incomplete actions on expiry

["Peter Furniss" <peter.furniss@erebor.co.uk>]

Issue name -- WS-AT: Incomplete actions on expiry

 

PLEASE DO NOT REPLY TO THIS EMAIL OR START A DISCUSSISON THREAD UNTIL THE ISSUE IS ASSIGNED A NUMBER.

 

The issues coordinators will notify the list when that has occurred.

 

Target document and draft:

 

Protocol:  WS-AT

 

Artifact:  spec

 

Draft:

 

AT spec cd 1

 

Link to the document referenced:

 

http://www.oasis-open.org/committees/download.php/17325/wstx-wsat-1.1-spec-cd-01.pdf

 

Section and PDF line number:

 

ws-at section 10, lines 503/505
 participant table: Expires times out/Active, /Preparing
ws-at: seciton 6.1, line 371

 

Issue type:

 

Design/Editorial

 

Related issues:

 

Issue Description:

 

The cells for Expires Times out for Active and Prepared states should include the (internal) Initiate Rollback and Forget actions.

 

Issue Details

 

Expires Times out should trigger the same internal events as receipt of rollback - otherwise the state machine will never exit.

 

(An argument could be raised that the "initiate rollback" action is superfluous, since the corresponding actions on the bound data [the application-dependent state that will be changed by the transaction if it commits] for preparing and committing are not mentioned. But the point of this issue that Expires Times out and received rollback should trigger the same internal actions, however those are specified)

 

Proposed resolution

 

Make the Expires Times out cells for Active and Preparing states the same as the Rollback cell.