Janne:
There is currently no support for the notion of a block listener. Some pieces are in place but the overall logic concerning event propergation by a container is under the "work-in-progress" category. This is somewhat tied to the work related to internal JMX management and the propergation of events via jmx attribute change event structures. Unfortunately this is non-trivial and really needs to be thought out properly as there are questions concerning location of classes with respect to classloaders - isolating listeners classes from components, etc. These issues together with support for plugable ECM/Fortress component handlers and Phoenix migration tools are addressed in the roadmap.
The good news is that support for container events is right up high on the list.
Steve.
Janne wrote:
My only remaining obstacle in converting to Merlin is the lack of a BlockListener interface. My application uses BlockListener to provide a graphical splash screen for monitoring the application startup. In case of applicationFailure the splash screen provides a human readable in your face error message about the cause of the exception.
Is there something even remotely similar in Merlin? Monitoring the application startup is not important but trapping the exception that causes application startup failure is.
--
Stephen J. McConnell mailto:[EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
