NEW ISSUE: WS-C: Clarify which endpoint is used to detect duplicateparticipant registrations

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

Issue name -- WS-C: Clarify which endpoint is used to detect duplicate 
participant registrations

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-C

Artifact:  spec

Draft:

WS-C spec CD 0.1 uploaded

Link to the document referenced:

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


Section and PDF line number:

ll. 317 - 321. Section 3.2, "Registration Service"


Issue type:

Design/Editorial


Related issues:

None
 

Issue Description:

Current text from resolution to 007 implies that 
/ParticipantProtocolService endpoint can be used to detect duplicate 
registrations.


Issue Details:

ll. 317 - 321 read:

"If a participant sends multiple Register requests for the same 
activity, the participant MUST be prepared to correctly handle duplicate 
protocol messages from the coordinator. One simple strategy for 
accomplishing this is for the participant to generate a unique reference 
parameter for each participant Endpoint Reference that it provides in a 
Register request. The manner in which the participant handles duplicate 
protocol messages depends on the specific coordination type and 
coordination protocol."

The sentence beginning "One simple strategy ..." is ambiguous (at best) 
about which EPR is being referred to. The Register request supplies a 
/ParticipantProtocolService EPR, and a wsa:ReplyTo EPR. The strategy 
being discussed here can only work if the WS-A [reply endpoint] has a 
value that unambiguously identifies (for the registering service) the 
participant. The PPS EPR is irrelevant.

Further, message ids could be used by the registering service to achieve 
the same level of knowledge of duplication.


Proposed Resolution:

Option 1:

Replace the sentence beginning "One simple strategy ..." with the 
following sentence:

"One simple strategy for accomplishing this is for the sender of 
Register to ensure that the the WS-Addressing [reply endpoint] Endpoint 
Reference that it provides in a Register request identifies the 
participant unambiguously from the sender's standpoint."

Option 2:

Replace the sentence beginning "One simple strategy ..." with the 
following sentence:

"This can be accomplished either by the sender of Register keeping track 
of the message ids of Register messages that refer to the same 
participant, or by the sender of Register ensuring that the the 
WS-Addressing [reply endpoint] Endpoint Reference that it provides in a 
Register request identifies the participant unambiguously from the 
sender's standpoint. Each of these techniques will allow duplicate 
RegisterResponses which refer to the same participant to be detected by 
the requester."