posted 15 years ago
You think correctly. A session-scope object is constructed once and remains until the session is invalidated unless you explicitly remove it from the session context. To be precise, it retains state.
One of the things that complicates this is that if the session object was reset, the "back" button wouldn't operate as expected. However, this can be annoying when moving forward, because what you want in your particular case is to reset the state of the object.
Probably the best way of resolving this is to supply the bean with a public method named "reset()" or "init()" or something like that. Then inject the session object into whatever object controls navigation towards whatever page(s) use the session scope object. Invoke init/reset() on the pbject as part of the action process that sends the user to the session-scope object pages.
"Disappointing" and "Utterly Horrible" are not equal.