Niclas Hedhman wrote:
Stephen McConnell said:
There is a semantic difference between resolving a dependency and service discovery. A dependency is something structurally bound to the component type. A component that requires a service discovery service should be declaring this as a dependency (in an ideal world). Unfortuately we are dealing with a historical context in which the semantics of type based dependencies and service discovery have been implied on a single interface (ServiceManager).
This conflict raises an important issue. If a component requests something that is not a dependency, does this action represent an error or does the action represent a ligitimate service discovery request?
This is why I would "promote" the solution of setAbc() for dependency resolution and a more generic lookup() for service discovery.
Sort of agree but I think something related to constructors for dependencies is more interesting than the setAbc().
Steve.
Niclas
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
Stephen J. McConnell mailto:[EMAIL PROTECTED]
Sent via James running under Merlin as an NT service. http://avalon.apache.org/sandbox/merlin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
