NEW issue: WS-C: ReplaceParticipant

[Mark Little <mark.little@jboss.com>]

Issue name -- WS-C: ReplaceParticipant

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:  Coord

Artifact:  spec / schema

Draft:

Coord spec working draft uploaded 2005-12-02

Link to the document referenced:

http://www.oasis-open.org/committees/download.php/15738/WS-Coordination-2005-11-22.pdf 


Issue Type

Design

Issue Details

In order to coordinate long running interactions, it is necessary to 
tolerate failures and recovery situations within the scope of an 
activity (long running activity). Once a participant is registered with 
a coordinator,  the current specification implicitly mandates that 
recovery requires it to come back up on the same EPR in order that the 
coordinator can subsequently drive it through whatever protocol is used 
(e.g., 2PC). However, recovery on the same EPR cannot be guaranteed and 
is at best an implementation choice. Failure to recover on the same EPR 
will ultimately lead to more coordinated activities terminating in a 
failure state (e.g., aborting) because participants cannot be reached, 
even if they failed and recovered prior to the start of execution of the 
coordinator's protocol.

Proposed Resolution:

That we add a ReplaceParticipant operation that allows a registering 
service to instruct the coordinator service to replace one EPR with 
another EPR. Because EPRs are not currently comparable, a resolution of 
issue 7 or 14 is relevant to this issue.