Thanks... really? But in a classic J2EE scenario you don't
need to register the HttpSessionBindingListener implementations...
and the framework calls their "valueBound" and "valueUnbound"
methods whenever it is appropriate.
http://tomcat.apache.org/tomcat-5.5-doc/servletapi/index.htmlBack to Flex/FDS case... as my attribute being bound to a
HttpFlexSession implements the FlexSessionBindingListener listener,
I would expect the framework (FDS) to call its methods when the
session gets invalidated, correct? So no XML configuration settings
are required.
Basically, what I'm doing:
FlexSession fs = FlexContext.getFlexSession();
fs.setAttribute("test", new FlexSessionBinding());
..................................
private class FlexSessionBinding implements
FlexSessionBindingListener
{
...................
/**
* Session 'Bound' notification
*/
public void valueBound(FlexSessionBindingEvent event)
{
........................
} // valueBound
/**
* Session 'Unbound' notification
*/
public void valueUnbound(FlexSessionBindingEvent event)
{
// Cleanup resources held by the service
.......................................
} // valueUnbound
............................
} // end of class FlexSessionBinding
The valueUnbound() method does not get called when the
session is invalidated.
