Good time, devs.
Sorry for this message, but I will try to retry or rewrite something.
Carsten Ziegeler <[EMAIL PROTECTED]> (S&N AG):
(List)ServiceManager.lookupAll(Filter.class).iterator;
Hmm, yes, although it might be that this is against one of the basic design principles of Avalon: security.
For this reason I provide solution: Collectable interface.
But answers of Niclas Hedhman and Berin Loritsch move me to nowhere.
I don't see any other solution with IoC template for such task (lookup collection) and cann't see any security problem in provioded solution.
Security: If component know Interface (Key) for one class, it can resolve it. If component know subinterface of Collectable, it can resolve all components, that implement such interface (not only Collectable, but subinterface of Collectable). Is there any security problem?
A common falacy is that one might think they can actually achieve total security. This is impossible, but it is quite possible to get something so complex and so convoluted that it is unusable.
Start with what is the real need here. Then look at the current solutions, and what we see as a deficiency. I've kind of gotten lost, so this is what I am missing here.
--
"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning."
- Rich Cook
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
