[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [Bug 217] New: Add message sequencing specification
http://services.arjuna.com/wscaf-issues/show_bug.cgi?id=217 Summary: Add message sequencing specification Product: WS-CF Version: 1.0 Platform: PC URL: http://www.oasis-open.org/apps/org/workgroup/ws- caf/email/archives/200501/msg00019.html 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 The Coordination Framework (CF) specification seems to specify a number of procedures that involve the sending and receiving of more that one message. In these cases the sequencing of messages can be important. For CF and Context the sequencing may, in fact, be relatively straightforward, but unless it is clearly specified that remains uncertain. I suspect that in several cases the allowed sequencing is not trivial, even if it is not that complex. The current specification of CF only seems to have diagrams that show the message set and their directions, not their sequencing. The WSDL fragments only show input messages (and not what can be sent out). So they do not even show what messages are responses to what messages, let alone sequencing (which can not currently be expressed in WSDL). WS-Context does have some start charts, but could probably be improved. I therefore suggest that state tables or state charts are added to CF (and WS-Context checked to ensure its sequencing specification is crystal clear). ------- 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]