Another idea (I do not like HttpSessionBindingListener): On sessionDestroyed you should be able to get Session ID information.
So just write your method: MySessionDataDropper.drop(String sessionID) or (MyObject data) which will drop all data identified by sessionID. Imagine: You have one Hashtable (scope application) with objects for your session identified by key sessionID String. On sessionCreated you add some "pointer" to your temporary data On sessionDestroyed you just take the correct object and drop its data. Another way is to use finalizers (= I do not recommend). GG -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
