Hi Sergey, I've often thought about this too, it would make it easier to write software that dynamically inspects what implementations are available (eg. in GUI's where you might want the user to choose which one gets used), and also for tool development.
Cheers, Marcus On Mon, 2004-08-02 at 16:00, Sergey M Vladimrov wrote: > Another things to add (usefull for my project only, but may be not): > > ServiceManager: lookup mechanism for all implementation of specified > class. Usage pattern: > > Iterator filters = > (List)ServiceManager.lookupAll(Filter.class).iterator; > ... > > -----Original Message----- > From: Niclas Hedhman [mailto:[EMAIL PROTECTED] > Sent: Monday, August 02, 2004 5:00 PM > To: Avalon Developers List > Subject: Re: [Proposal] Avalon Framework 4.5 > > > On Monday 02 August 2004 20:35, Carsten Ziegeler wrote: > > Any chance to also add the proposed lookup mechanism using a Class > > and a key instead of just a String as ServiceManager currently does? > > Open for debate, but I doubt it would qualify as a compatible change, > since > container implementations would NOT compile against it. > > That leaves two choices; > 1. AF5.0 > 2. Another interface including the method(s), subing ServiceManager or > not. > > 2. is also borderline compatible change, on the same basis as the > constructor > injection was considered not to be compatible. > > I suggest that you raise the proposal once more on dev@, and we'll take > a good > shot at it, and see if something reasonable can be worked out. > > Cheers > Niclas -- ..... ,,$$$$$$$$$, Marcus Crafter ;$' '$$$$: Computer Systems Engineer $: $$$$: ManageSoft Corporation $ o_)$$$: Frankfurt am Main, Germany ;$, _/\ &&:' ' /( &&& \_&&&&' &&&&. &&&&&&&: --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
