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 to set up CurrentCompositeContext for the outermost, deployable composite (there's likely a more correct term). But it seems simpler to consistently have Tuscany set up this context as a step in the invocation chain rather than to have the host to have to set up the context correctly for both outer-level and nested composites. Or is there already such a notification mechanism for crossing Composite boundary in effect? (I apologize that I haven't studied the code extensively to understand this; I'm mostly relying on learning via running samples and stepping through the debugger). Scott On 7/18/06, Jeremy Boynes <[EMAIL PROTECTED]> wrote:
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]
