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 142] New: How does context service know the status ?


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

           Summary: How does context service know the status ?
           Product: WS-Context
           Version: 1.0
          Platform: PC
        OS/Version: Windows 2000
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Model
        AssignedTo: ws-caf@lists.oasis-open.org
        ReportedBy: peter.furniss@choreology.com
         QAContact: mark.little@arjuna.com


The context service reference (address) is not propagated in the context )
context service identifier is not dereferencable) and need not necessarily be 
co-located with the context manager (otherwise why are they different 
interfaces). Yet for all context types (?), the originating context service 
knows the current status of the activity and invoking complete will cause a 
status transition to Completing.

How do the activity participants know the state of the activity ?

How are the participants made aware of the transition to Completing ?

How does the context service know the transition from Completing to Completed 
has occurred ?

Obviously, a referencing specification could be devised that provided 
additional registration and status propagation facilities, and which imposed co-
location requirements (or at least common-knowledge requirements) on these 
services and the ContextService. But the status mechanisms should be part of 
that specification rather than the base context. This would allow the ref. 
spec. to define the status mechanism it needed (e.g. combining the 
activity.status and the completion status, if it so chose).



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