Hi everybody! My current solution required access access to the full lifecycle of the page. The only way I know is through IMonitor.
Afaik this can be done by setting application extension 'org.apache.tapestry.monitor-factory' or by overriding hivemind service point 'tapestry.monitor.DefaultMonitorFactory'. However this does not allow multiple IMonitors without letting the instances know of each other (and cascading method invocations). Is this true or did I miss something? Is there a better approach to monitor the lifecycle of a page? Best regards Peter --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
