It's possible. I've read this whole bug now, though, and I can't figure out where we could have went wrong, if we did. Unless there is some inherinet problem with using Hibernate and Tomcat (with regards to this bug), then I don't know what specifically we need to do to make sure that session objects don't persist between and across sessions. The object itself appears to be completely threadsafe on its own. I created an action where I instantiated an instance of one (outside of getting it from Hibernate), populated it with the list, dropped it into session, logged out, logged in and it behaved as expected. It wasn't there.
Preston >>> [EMAIL PROTECTED] 10/4/2005 8:29:57 AM >>> On 10/4/05, Preston CRAWFORD <[EMAIL PROTECTED]> wrote: > Tomcat 5.0.28. this should work. However try logging out the sessionIds and compare them to the jsessionid cookies, just to be sure. Maybe you are also hit by the tomcat session bug: http://issues.apache.org/bugzilla/show_bug.cgi?id=36541 Another option: send the action and the form and we'll check this :-) regards leon --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
