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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ws-caf message

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


Subject: [Bug 262] Extension of status type


http://services.arjuna.com/wscaf-issues/show_bug.cgi?id=262

mark.little@arjuna.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |LATER



------- Additional Comments From mark.little@arjuna.com  2005-06-16 11:29 -------
Voted to adopt:

During its existence an activity MAY report statuses (which SHOULD unambiguously
reflect internal states of the activity), in reaction to receipt of the message
wsctx:getStatus.

The referencing specification states whether statuses will be reported, and if
so, how they are named and defined. If an activity does not return statuses then
it MUST return a fault wsctx:NoStatusesDefined when asked to report a status.

If an activity does return statuses then it SHOULD report its current status
when asked; there is no notion of automatically informing services when a
specific state is entered. If an activity cannot report its current status but
may be able to do so in the future then it SHOULD return a fault
wsctx:statusUnknown. If an activity is unknown to the Context Service when it is
asked to report a status, then it SHOULD return a fault: wsctx:unknownActivity.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


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