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 163] New: WS-CF without Coordinator and Participant


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

           Summary: WS-CF without Coordinator and Participant
           Product: WS-CF
           Version: 1.0
          Platform: PC
               URL: http://www.choreology.com/external/ws-
                    cf.choreology_comments.htm#CHCF-5
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Text and diagrams
        AssignedTo: ws-caf@lists.oasis-open.org
        ReportedBy: tony.fletcher@choreology.com
         QAContact: mark.little@arjuna.com


Where: 2, page 9, para 4

With the removal of ALS from WS-Context, the middle sentence of this says that a
compliant WS-CF implementation doesn’t have to do anything. This seems a little
wide.  Presumably the intent is to cover coordination protocols whose propagated
context is derived from wsctx:context.

Is it meaningful in any case to claim to be using WS-CF when it is only acting
as a context service - and for a non-interoperable (or at least non-ws)
coordination capability?



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