Hopw about to requere that all such interfaces whould extends some
interface, like "Collectionable" (soory for my English).
If interface extends it, manager can collection. If not - throw
exception.
And, of course, manager disable returning all Collectionable objects.
Only subinterfaces.
For eample:
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
-----Original Message-----
From: Carsten Ziegeler [mailto:[EMAIL PROTECTED]
Sent: Monday, August 02, 2004 6:13 PM
To: 'Avalon Developers List'
Subject: RE: [Proposal] Avalon Framework 4.5
Niclas Hedhman wrote:
>
> On Monday 02 August 2004 21:56, Farr, Aaron wrote:
> > > From: Sergey M Vladimrov [mailto:[EMAIL PROTECTED]
>
> > > Iterator filters =
> > > (List)ServiceManager.lookupAll(Filter.class).iterator;
>
> > Personally, I'd like
> > to see something standardized along these lines.
>
> Agree, although I think it will be misused at times :o( ,
> a.k.a Flexibility Syndrome.
>
> Carsten, can you accommodate for this in the proposal as well ?
>
Hmm, yes, although it might be that this is against one of the
basic design principles of Avalon: security. You have to know
which component you want to lookup, there is no "give me all"
functionality.
Anyways, yes, I will add this and we can decide/discuss it.
Carsten
---------------------------------------------------------------------
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]
