Using Cross-Context Flows

The primary usage of Cross-Context Flows will be for Component Based Development, where transactional components are deployed independently.

Note: For information about Component Based Development, see the Component Standard 3.1.1 white paper.

Other usage of Cross-Context Flows could occur:

To override one part of a deployed ear file to facilitate change or testing.
To transition from one application to another.
To isolate separate parts of the application for different models and different support groups.