> -----Original Message----- > From: Marcus Crafter [mailto:[EMAIL PROTECTED] > > I know this discussion is not new - just wondering what the advantage is > with the first approach?
If I remember correctly, part of the advantage of string lookups is that you can use arbitrary service naming -- not just ROLE naming. This is particularly helpful when you have more than one component fulfilling the same ROLE and need to retrieve a specific instance. Though I think greater clarity on service naming conventions and preferred lookup techniques would be nice. I've been meaning to work on this and put together some documentation, but haven't had the time. For example, at some point we need to work out how a component can be dependent on services (ie- does serviceManager.lookup() ) whose names are not known until runtime. This has direct impact to the use of the @avalon.dependency tag being proposed. Should components be allowed to lookup services they don't declare a dependency on? How can arbitrary dependencies be identified? jaaron --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
