On Nov 6, 2007 10:16 PM, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
> This is not so cool ... I wonder if there's a way we could build a bit > more of an event bus into Tapestry. Now that Tapestry knows all the > pages at startup, we could do some pretty sophisticated things: Have > annotations that register methods for application events, rather than > page events. So to interact with the flow of the application and render based on event results... > The framework could automatically load page instances in order to > receive such events. Could this be coming from other components and/or services only or even from external calls like some sort of REST calls? > It implies a bit more work at startup: all page classes will need to > be transformed at startup, or at least, on first request. It's an > interesting idea though. Very very interesting and very powerful... -- Massimo http://meridio.blogspot.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
