On Sep 22, 2006, at 9:01 AM, Raymond Feng wrote:
I prefer not to have the receiver code to deal with the operation
mapping. The databinding framework should be able to handle it.
Can we directly locate a composite service? I had an impression
that the proxy can only be created out of the component.service or
composite.reference as defined by the SCA C&I spec.
CompositeContext.locateService() has the following statement:
T locateService(Class<T> serviceType, String serviceName);
"serviceName" can either be "<component-name>/<service-name>" or
"<reference-name>". Composite service is not a valid target and I
got a confirmation from Jeremy the other day on IRC.
AIUI a proxy is only created
1) by a implementation type that want to inject a strongly typed
interface implementation to an instance it is managing
2) by locateService to return a strongly typed interface
In both cases, the service contract for the proxy is defined by the
Java Class of the interface it is implementing which will *always* be
local to the client (either the instance or whoever called
locateService). What that is wired to is irrelevant.
--
Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
