Muhwas,
Your objection to the locateService API seems to be
the need to pass the business interface class. As Simon
noted, this doesn't go away with the new v1.0 API.
If the business interface were not passed as a parameter,
what interface would you expect the returned proxy
to implement?
Dave
----- Original Message -----
From: "Simon Laws" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, April 19, 2007 7:35 AM
Subject: Re: using service name to call a service
On 4/13/07, muhwas <[EMAIL PROTECTED]> wrote:
Hi guys,
I was wondering if there is any way to get a reference
to web service interface using service name (in SCDL
file) only instead of doing
compositeContext.locateService(ClassName.class,"composite")
thank you,
muhwas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi Muhwas
I'm not sure what the options were on M2. In the latest software (in the
trunk of our svn respository) we are moving to implement V1.0 of the SCA
specifications. The emphasis here is on component context although how a
component context is obtained is not specified. In the trunk
implementation
we currently have an embedded host container that allows a component
context
to be returned in the following way.
SCARuntime.start("my.composite");
ComponentContext context = SCARuntime.getComponentContext
("MyComponentName");
From there the spec says that you should be able to do (not sure it quite
works like this yet)
MyService service = context.getService(MyService.class, "MyServiceName");
I know this doesn't answer your question re. M2 but hopefully gives you an
idea of where we are going.
Regards
Simon
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
