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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ws-tx message

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


Subject: NEW issue: WS-C: Add new fault CannotRegisterParticipant


Issue name -- WS-C: Add new fault CannotRegisterParticipant

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
WS-Coordination schema contributed by input authors, not yet uploaded to 
Working Drafts folder

Link to the document referenced:

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

Section and PDF line number:

Section 4 "Coordination Faults", l. 371 onwards


Issue type:

Design


Related issues:

Issue [] WS-C: Appropriate categories of fault
Issue [] WS-C: Add new fault CannotCreateContext


Issue Description:

Registration Service should be able to communicate inability to register 
a participant


Issue Details:

Faults in WS-C should be divided into two categories: those which apply 
to the process of context creation and
registration (or which apply to the misuse of the conversational channel 
created by registration), and those
which are basic faults available to all coordination protocols.

Under the first category, it seems reasonable to expect that a 
Registration Service may not be able to satisfy
a request to register a Participant. Reasons might include: capacity 
constraints; authorization failure;
resource failure (loss of connection to persistence store, for example).


Proposed Resolution:

1) Insert new Fault description (order in section an editorial matter) 
as follows:

4.x Cannot Register Participant

This fault is sent by the Registration Service to the sender of a 
Register to indicate that the Participant
could not be registered.

Properties:

[Code] Sender
[Subcode] wscoor:CannotRegisterParticipant
[Reason] Participant could not be registered.
[Detail] unspecified


2) Add new enumeration to schema type ErrorCodes:

      <xsd:enumeration value="wscoor:CannotRegisterParticipant"/>



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