Re: [ws-tx-comment] WS-BusinessActivity Specification

[Ian Robinson <ian_robinson@uk.ibm.com>]

Dominik,
The WS-BA spec is prescriptive about
how a coordinator must manage participants within a business activity scope
but is not prescriptive about the relationship between parent and child
activity scopes. In your example, activites B, C and D are each sibling
child activities of A. One way of relating a child activity to its parent
is to make the coordinator of a child activity a participant in its parent
activity, although the specification does not require this. Even though
the Coordinator for B is an AtomicOutcome coordinator (and the outcome
of all participants within the scope of B must be the same), if it were
also a participant of A it would be a participant in the MixedOutcome activity
A. Continuing this example, the completion of the AtomicOutcome work of
B would result in a wsba:Completed protocol message to A (in B's role as
a participant of A in this example). Once A received all its wsba:Completed
signals, it would consult application logic to determine which participants
to close and which to compensate.

Regards,
Ian Robinson

"Dominik Heller" <Dominik.Heller@gmx.net>

17/01/2008 10:08

To	ws-tx-comment@lists.oasis-open.org
cc
Subject	[ws-tx-comment] WS-BusinessActivity Specification

Hello,
I am reading through the WS-BusinessActivity Specifiaction right now and
I am not sure if I understood the concept of the Business Activity scopes
correctly. Well to picture the way of my understanding right now I describe
a little scenario:
the top node of the Business Activity is a MixedOutcome Coordinator A which
has three childs say, one AtomicOutcome Coordinator B with two childs and
two separate MixedOutcome Coordinators C and D with two childs each.

So do I guess right that every coordinator is contained in a separate Web
Service because of separate business logics and then is just plugged together
 to a Business Activity?

The WS-BA spec is talking about nested scopes and that a business application
is allowed to select which child tasks are allowed in the overall outcome.
So in the end this means that the business logic of the Coordinator C chooses
which of his childs has to close and which has to compensate and then notifices
the Coordinator A that it is ready for closing or compensation, right?


Well thanks in advance for your help

Dominik Heller
-- 
Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten 
Browser-Versionen downloaden: http://www.gmx.net/de/go/browser

This publicly archived list offers a means to provide input to the
OASIS Web Services Transaction (WS-TX) TC.

In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.

Subscribe: ws-tx-comment-subscribe@lists.oasis-open.org
Unsubscribe: ws-tx-comment-unsubscribe@lists.oasis-open.org
List help: ws-tx-comment-help@lists.oasis-open.org
List archive: http://lists.oasis-open.org/archives/ws-tx-comment/
Feedback License: http://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
Committee: http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ws-tx

---

Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

S/MIME Cryptographic Signature