quote:Originally posted by: Robert CsikiThe valueUnbound() method does not getcalled when the session is invalidated.did you try manually remove the attribute fromsession? will the valueUnbound() be called then?

yes, messed it up a bit with my case with SessionListener,sorry

you need to register it or in web.xml or inservices-config.xml (latter requires it to extendAbstractBootstrapService)here is my services-config.xml <services> <service-include file-path="messaging-config.xml" /> <service-include file-path="remoting-config.xml" /> <service-include file-path="proxy-co...

>>This is because multiple Flex client applications mayshare a single HttpSession so a valid HttpSession does not indicateThat is an interesting part. Is there a way to avoid sharingsessions between multiple client apps? May be some configsettings?

yes, if the browser just closed, without calling *log off*method, then i listen to destroying sessions, get client id from itand do log off for this client (clearing serverside data on it andso on)i tried to tune timeout setting at <session-config> inweb.xml - but the session still dies only 5 minut...

Hello Robert,I have the same problem.I got a java serverside with a flex client. So at serversidei created a class that extends AbstractBootstrapService (so it isloaded as Flex Service from services-config.xml) and it implementsFlexSessionListener interface - listens for sessions created andclosed. ...