Would you agree it would make sense for Tuscany to provide this function
rather than the host env?
If this is the host env's job then it must get a notification every time a
Composite boundary is crossed in the case of recursively nested
composites. True it may be easy enough for the host env
Does Tuscany, now with Chianti, take responsibility for setting up the
CurrentCompositeContext?
When I last understood the relevant code, at M1, Tuscany was more or less
requiring the host environment to set this up (then CurrentModuleContext).
This was done with Tomcat via the TuscanyValve, for
Responsibility still lies with the host environment.
In the launcher's case, it is the J2SE (command line) host
environment so it sets up the context before calling the application
code; it is kind of similar to a J2EE application client container.
We do a similar thing in SCATestCase to
