Java Reference
In-Depth Information
In this example, the
<flow>
activity is kicked off when a customer makes a purchase. The in-
vocations of the customer contact service and the shipping service both need to happen right
after a sale is made. They don't require input from one another, and executing one doesn't
have to wait until the other is complete. The flow itself completes when all of its child activit-
ies have completed.
NOTE
You can also add a
<documentation>
element as a direct child of a
<flow>
, which allows you to
enter arbitrary text data to indicate how the flow works.
This is useful in many situations, particularly in distributed service environments where the
services do not rely on shared processing resources.
See Also
It is frequently the case that you will need to synchronize the execution of certain activities
within a flow; that is, you may want to run some activities concurrently, but then force one to
wait for another to complete. Check out
Synchronizing Activities Executing in Parallel
.
