Completely Separate

A - V1.1 and V1.0 composite in the same domain

Handling both v1.1 and v1.0 policies

...

Need policies in both namespaces represented. Create side by side defintions.xml files in extensions

A-1 Just running in the same domain

Need both types of processors and a shared model. With separate nodes, v1.0 and v1.1 runtimes could be seaprated. Doesn't seem to be much advantage over independent operation

A-2 Running and interacting in the same domain

Need both types of processors and a shared model. With separate nodes, v1.0 and v1.1 runtimes could be separated. Need an interoperable binding.sca (we have this at the moment as it is based on binding.ws)

B Full integration V1.1 reusing V1.0 composite

Need both types of processors and a shared model. Need a shared runtime, i.e. some flexibility in builders, pluggable conversations and callbacks. Not sure about activation.

C V1.1 Domain that uses V1.0 composite to implement components