Hi all,
1) Compensate: The mixed outcome is the notion of the entire BA, identified by a coordination context. In order to understand how this can be implemented image the protocol instance for each participant-coordinator pair. The mixed outcome means that there is no strict rule between the results of one such instance and another. That means that dependent on the business case you can have different behaviour of the BA. This is the core idea of BA and this flexibility is desired. Here are two examples of different business cases: a) WS-BA is "simulating" WS-AT. So a special form of mixed outcome is the atomic outcome b) WS-BA is used for an auction process. The initiator requests for a bid and the participants answer. The best bid wins, so the participant receives a confirmation and all other participants receives compensation. How this can be implemented? The coordinator should know how to act, a feature not covered by specification. Either it is externally triggered (additional SEI for transmittion of decisions on each BA-Protocol Instance) or internally, which means the "understanding" of the Business Logic => Workflow Engine 2) Cancel The cancel message is designed in order to inform the participant in 1-st phase (active / completing) that the BA will stop. 3) Exit Exit has technical and business meaning. From the technical point of view other BA-instances are not affected (there are no rules in BA about it). From the business point of view there can be a usecase for doing something... -- Dipl. Ing. Simon Zambrovski Research Assistant Hamburg University of Technology Institute of Telematics Schwarzenbergstrasse 95 D-21073 Hamburg Phone: +49 40 428783704 ________________________________ From: bimalee salpitikorala [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 10, 2007 10:41 AM To: [email protected] Subject: Issues in ws-BusinessActivity specification Hi all, we came across few questions while we are implementing the ws-BusinessActivity specification. When implementing the MixedOutcome coordination type there is a requirement to identify the important(critical) participants so that if one fails the whole business Activity is effected and the other participants should be sent with the "Compensate" message. We thought of giving that responsibility to the user through an interface but have a vague idea of how to identify those participants. The other problems that needs support are the meaning of Cancel (When coordinator send a cancel message what does the participant have to do, Other than sending the cancelled message?) Is it possible to handle it like "abort" in Atomic transactions? And the "Exit" message if an exit message received by the coordinator is there anything to be done other than sending "Exited"? If an important participant exit in the middle of it's processing what has to be done by the coordinator? Hope you would help us to clarify these problems. thank you! regards, bimalee
