Oh blast it, never mind. It's still invalidating itself base on the time when getAttribute is called. I guess I'm just going to create another level of indirection and store all my attributes in another store hashed by session id.
sorry for the wasted bandwidth.
Roger
Roger Desroches wrote:
Hi,
I'd like to change the order of the calls in the script session invalidate so that the sessions invalidate isn't set to true until the script session manager has a chance to do invalidate work.
I have a registered ScriptSessionManager of my own that is trying to do work on some stores, but I can't get the attributes out of the ScriptSession because it's invalidated. therefore, I'd like to set the invalidated flag AFTER the manager is done working with it.
public void invalidate()
{
synchronized (invalidLock)
{
// the following two lines are swapped compared to current code
manager.invalidate(this);
invalidated = true;
}
}
What do you think?
roger
