Ok, although with non-SCA clients which component would that be? Does there need to be a new something like implementation.web but for JSE clients? or could there be a "virtual" component that has references for all the toplevel component services in the domain (which is kind of what we have now with SCADomain.getService right?).
...ant On Thu, Apr 17, 2008 at 9:10 PM, Yee-Kang Chang <[EMAIL PROTECTED]> wrote: > Just thought to follow-up to see if we will do this .. > > Perhaps SCADomain can be extended to return the ComponentContext for a > particular component? > > Thanks. > > On Wed, Apr 2, 2008 at 6:37 PM, Kevin Williams <[EMAIL PROTECTED]> > wrote: > > The current JUnit tests (iTest and vTest) make use of the non-standard > > SCADomain.getService API to get a handle to an SCA service. Are there > > any plans to provide an API to get a ComponentContext as outlined by > > the SCA Java Annotations and APIs specification? I would like to > > stick to stick to specified APIs as much as possible in vTest. > > > > > > 1.4.2.1. ComponentContext > > Non-SCA client code can use the ComponentContext API to perform > > operations against a component in an > > SCA domain. How client code obtains a reference to a ComponentContext > > is runtime specific. The following > > example demonstrates the use of the component Context API by non-SCA > code: > > > > ComponentContext context = // obtained through host > > environment-specific means > > > > HelloService helloService = > > context.getService(HelloService.class,"HelloService"); > > > > Thanks. > > -- > > Kevin > > I don't remember any discussion about this so i guess there are "no plans" > yet to change it. I agree it seems like we should though. > > ...ant >
