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 set up the environment before
calling the user's TestCase (we do it in setUp).
--
Jeremy
On Jul 18, 2006, at 6:52 PM, Scott Kurz wrote:
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 example, (which
I'm not
counting as part of Tuscany proper).
I see in chianti that
org.apache.tuscany.core.launcher.CompositeContextImplis setting up
CurrentCompositeContext but I'm not sure what to make of
this. Is Tuscany already setting up CurrentCompositeContext or
might this
be an area in which to propose an improvement?
Thanks
Scott Kurz
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
