What do you think about creating a custom lifecycle for the subscribe
Operation on this event router/bus concept. BTW Berin has already done this with GUIApp but I'd like to see this sort of thing make its way into Merlin.
Alex, IMO I think this is better done as a facility instead of a custom lifecycle extension. In the way that we are doing HTTP-driven components and (JMS) message-driven components using facilities, I think a facility to implement event-driven components is a good candidate.
Timothy
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
