Damn it, I really hate the Servlet API sometimes. It doesn't provide a HttpSession.isInvalidated() method.
It doesn't say how session data is supposed to be replicated. If you use WebLogic, then you have to keep invoking setAttribute(). But if you do that in Tomcat, it looks like it calls valueUnbound() [probably followed by valueBound()]. I guess I'm going to have to re-instantate a JVM system property to control whether to to a HttpSession.setAttribute() at the end of the request cycle, so that it can be turned on just for WebLogic. Perhaps I should start requireing a more recent Servlet API than 2.1 ... I think there are other notifications I need in later versions of the API. But that might screw WebSphere users. ----- Original Message ----- From: "Jason Owens" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, September 06, 2002 6:52 PM Subject: Bug? > Hi Howard, > > I'm not sure if this is a Tapestry bug or a Tomcat bug (I'm using > 4.0.1), but in ApplicationServlet, you call session.setAttribute(), to > store the engine. Sounds good, but the catalina session object then > calls valueUnbound(), which triggers a cleanupEngine(). > > The implication is that cleanupEngine loads the active pages, which > calls attach(IEngine)... The net effect (and it may be caused somewhere > else) is that I never get access to that page again! In other words, > every load/refresh of that page detachs it, then immediately reattaches > it, and the next time gives me a new page (since presumably the page > was removed from the pool and never stored again). > > What do you think? > > -Jason > > ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
