OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

sca-j message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: ISSUE 4 - Dependency reinjection


Title: ISSUE 4 - Dependency reinjection

There was an action item to find a better approach for describing the relationship of service reference instances, wiring, and what gets called in the end (aka the target).

Ron, Peter, and I had some short discussions on this and came up with the following assertions:

1. Services have an address: Service Component Services have an SCA URI, otherwise bindings provide a URI or some equivalent addressing data.

2. Service reference instances are a client view to a service address: It consists of the service address and (if available) a conversation handle (e.g. an ID, a proxy) and interface information.

3. The address and interface association does not change over the life time of a service reference. An exchange (re-deployment) of the addressed service's implementation SHOULD not invalidate a Service reference instance. Technical constraints may however lead to a de-facto invalidation of service reference instances (e.g. cannot consume previously handed out data).

Or, in one paragraph:
Services have an address, which can be an SCA URI in the case of a service component service or some other addressing data provided by a binding declaration. A service reference instance is a client view to a service address. It consists of the service address and (if available) a conversation handle (e.g. an ID, a proxy) and interface information. The address and interface association does not change over the life time of a service reference instance. An exchange (re-deployment) of the addressed service's implementation SHOULD not invalidate a Service reference instance. Technical constraints may however lead to a de-facto invalidation of service reference instances (e.g. cannot consume previously handed out data).

Thanks,
  henning

Ps.: I believe that ComponentContext.getServiceReference(...) should provide such a client view according to the most current wiring.



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]