Steven Harris wrote:
I believe I read in one of the docs, in a NOTE that selectors were no longer the preferred way of
doing things. I was wondering if someone could point me to some-more info on this?
The Merlin implementation does not support Selector semantics because the query semantics is not specified. This means that any selector implementation is implementation specific. The approach in Merlin is to require component authors to make selection semantics explicit by defining a specific selection service and corresponding implementation. The consumer component then defines an explicit dependency on the specific selection service - e.g.
@avalon.dependency type="org.somewhere.ConnectionSelector"name="connections"
The component recieving the service manager then invokes lookup for "connections" and then requests a connection using parameters specified under the supplied service interface - e.g.:
ConnectionSelector selector = (ConnectionSelector) manager.lookup( "connections" ); // generic
Connection connection = selector.createConnection( 1234, TRANSACTIONAL ); // specific
Stephen.
--
Stephen J. McConnell mailto:[EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
