In addition to the JSF-Spring suggestion, you should check out the following standard Servlet API capabilities:
* HttpSessionBindingListener - lets an instance itself be notified when it is bound or unbound into a session (the latter happens when the session expires). * HttpSessionAttributeListener - lets an external listener instance be notified when attributes are bound or unbound from any session in the application. * HttpSessionListener - lets an external listener instance be notified when sessions are created or expired. Craig On Tue, 22 Feb 2005 11:22:17 +0100, Sascha Schmidt <[EMAIL PROTECTED]> wrote: > > Hello! > > I'm working on a JSF project that has some backing beans in session scope. > Now we have the need to register these beans at a messaging system to > exchange some data. But if the backing beans are registered at a messaging > system they will never be freeed by the garbage collector. The question is: > are there any lifecycle methods that are invoked when a backing bean is > destroyed (end of session)? Is it possible to monito and observe backing > beans? > > Thank you! > > Cheers, > Sascha
