Hi Niclas, > I'm slightly in the dark of what you are trying to do. thanks for the fast reply. What we are trying to do is quite simple: - we have Display component that would like to know if there are any providers of softkey events (like the softkeys on an ATM or a mapped PINPad) in the system, in order to register itself as a listener for these events and - as a slave - provide feedback to the customer by setting the appropriate button in a "pressed" state in the current display. - the display component works fine if there is no softkey event provider in the system, but hte same scenario is valid for other "just interested" clients.
It feels like there a some main patterns: 1. Should there be a concept of "non-fatal" dependencies that for some components are "nice to have" but that not break the assembly if there is no implementation in the system? 2. Is that maybe a case where the simple observer pattern (that needs to know the event provider directly) that is used by several clients on a component should be replaced by a global event mediator where everyone is supscribing to everything and filtering outthe interesting things - isn't that something that Alex took up for some time ago? I think that would introduce a lot of events just for a simple scenarios sake - I like the approach of avalon with not withering down everything to AOP and events ;) 3. Could interceptors/AOP help to get hold of the compoenents as the start up in order to filter out the "non-fatal" deps? Hope hat helps a bit :) Cheers /peter
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
