Hi all,
That's what we did. The initiator provides a "match code" (which must be
unique within a context) to the coordinator who returns a
CoordinationContext tagged with an registration ticket.
When that CoordCtx object is used by a participant to register, the
coordinator will attach the match code to the corresponding match code.
The coordinator also assigns a unique participant identifier to the
participant.
At this moment I'm more or less concerned only about the non-initiator
case.. In that case what I have in mind is to add that unique
identifier to the registration epr of the coordination context which
we are putting to the outgoing business message. We can do this at
the outgoing handler. In this case we do not need to obtain the coor
context each time...
A side effect of this implementation is that a particular coordination
context object may only be used for one registration, and that the
coordinator will reject participants who try to register for an
already-in-use or non-registered matchcode.
I don't think it as a limitation.. rather a feature :)..
Exactly. None the less, the initiator cannot be sure if the participant
will really cancel until it receives a Canceled or Completed message.
I guess a participant could anyways just ignore Cancel and always report
Completed, so one shouldn't rely on Cancel too much.
Yeah... But I think we can consider it as good practice for the
participants to support cancel. By supporting the "Cancel" things
become much better If the participant has not done the actual when it
receives the "cancel", rather than compensating later.
The WS-BAI-Specification has a section on this problem, see section
3.4.1 in the upcoming PDF document.
What's exactly is the WS-BAI spec.. Can you provide us an pointer....
Who is doing it..
Thanks a lot,
Thilina
>> The user selects any number of participants,
>
> Can we select exactly one identified participant..
Yes, by providing the corresponding matchcodes, e.g. "Cancel
participants [Pa, Pb]".
See the upcoming WS-BA-I draft.
Best regards,
-hannes
--
Thilina Gunarathne
WSO2, Inc.; http://www.wso2.com/
Home page: http://webservices.apache.org/~thilina/
Blog: http://thilinag.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
