1. can you avoid using a selector by declaring a dependency on a selection service?
you're right, this is the most respected solution.
2. if you are absolutely locked into selector semantics, how urgent it is?
I am not. But I can think of a couple of scenarios in which such a functionality would be required (SEDA architecture for example).
3. workarounds to the problem are possible via cascading containers
maybe this has been discussed before. Do you mean that a component behaving as a container can lookup all of its child components? Can u explore more or redirect me to some prior discussions?
4. think about option (1)
5. consider option (4)
6. your best bet is to go with any option less than 2 or greater than 3.
thks.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
