I think I may have been a little unclear in my explanation.
I have a system of object for security checking. The only object that is
used in the web part of my application
is a proxy to my User objects. This proxy also implements the
HttpSessionBindingListener interface. In the
valueUnbound()
Vernon,
Yes, there are some possible timing issues with using object references attached to
the session in any class implementing HttpSessionBindingListener. I believe that the
order which references are unbound is unpredictable.
When I did this, I ran into the same problem and compromised by
What do you have stored in the session that has to be checked on?
I only need the reference to my UserProxy object, so I call the logoff
method like so:
Security.doUserLogoff( this );
if you need other things that are in the session, is it feasible to keep
them elsewhere and key
them by whateve
3 matches
Mail list logo
