- From: Charlton Barreto <charlton_b@mac.com>
- Date: Tue, 23 Jan 2007 16:37:19 -0800
- To: Gary Brown <gary@pi4tech.com>
- Cc: "'WS-Choreography List'" <public-ws-chor@w3.org>
+1 to your proposal: "Where a roleType has multiple record elements associated with an exchange or timeout, only one of these record elements MAY define a causeException attribute". -Charlton. -- charlton_b@mac.com +1.650.222.6507 m +1.415.692.5396 v On Tuesday, January 23, 2007, at 05:49PM, "Gary Brown" <gary@pi4tech.com> wrote: >In section 6.2.3, it says: > >"When two or more record elements are specified for the same roleType in an >interaction, with their causeException attributes set to indicate that an >exception should be caused, then one of the exception types MAY be caused. >The throwing of an exception has a non-observable predicate condition >associated >implicitly with it, that decides if an exception is caused" > >Due to the fact that this describes a non-observable predicate making >the decision about which (if any) of the multiple exceptions are thrown, >it means that it may be difficult for the other participants to >deterministically identify the same path through the choreography. > >I would suggest changing the sentence to prevent an exchange (or >timeout) having multiple records with exceptions (i.e. have atmost one >record with causeException set). A replacement sentence could be: > >"Two or more record elements, that are specified for the same roleType >in an interaction, with their causeException attribute set to indicate >that an exception should be caused, MUST not be permitted." > >OR > >"Where a roleType has multiple record elements associated with an >exchange or timeout, only one of these record elements MAY define a >causeException attribute". > > >Regards >Gary > > >
Received on Wednesday, 24 January 2007 00:38:13 UTC