Sorry, I don't understand your choise. Can you provide example? MyService1 and MyService2 doesn't know anything about each other. And they needn't know anything about caller (and there may be more than one of they).
If you are talking about registing themselves manually, it's bad idea IMHO. I don't need avalon for this. -----Original Message----- From: Niclas Hedhman [mailto:[EMAIL PROTECTED] Sent: Monday, August 02, 2004 9:23 PM To: Avalon Developers List Subject: Re: [Proposal] Avalon Framework 4.5 On Monday 02 August 2004 23:52, Sergey M Vladimrov wrote: > Hopw about to requere that all such interfaces whould extends some > interface, like "Collectionable" (soory for my English). Collectable is probably the word you are seeking. > interface MyFilter extends Collectionable > > MyService1 implement MyFilter > MyService2 implement MyFilter > > ServiceManager.lookupAll(MyFilter.class) return {MyService1, MyService2} > > ServiceManager.lookupAll(Collectionable.class) throw Exception > > ServiceManager.lookupAll(Object.class) throw Exception Java language works better :o) It is an interesting thought, since you are basically saying, "I know there are a bunch of components intended for me, so bring them on..." OTOH, if the component to be looked up is dedicated for this purpose, why isn't the MyService1 looking up the "other guy" and adds himself over a component specific method?? Cheers Niclas -- +------//-------------------+ / http://www.bali.ac / / http://niclas.hedhman.org / +------//-------------------+ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
