Thanks for that Wendy.
I thought it might be your suggestion about caching so I added code to the JSP's to disable the browser cache. I also added logging to display the session ID's and they are indeed different: >From the JSP that invokes the modal dialog: sessionID = 0E07F517D6AD7002500A46A6B37798F9 >From the modal dialog JSP itself: sessionID = 74D52752E99875A00132DE792311124B This seems very odd. Does anyone have any ideas why they should be different? It only happens intermittently but once it starts to happen once has to shut down TC to recover it. TIA -Adam -----Original Message----- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: 11 April 2005 18:23 To: Tomcat Users List Subject: Re: Session object not the same in different JSP's From: "Adam Lipscombe" <[EMAIL PROTECTED]> > Most of the time this works fine. However occasionally the session > object that is used by the caller (i.e. the JSP) and the dialog are > not the same instance. i.e. The ActionErrors Object is stored in > session X but the modal > dialog JSP uses session Y. How do you know, are you printing out the session id? If you're just going by the fact that you're not getting the correct list of errors, could the browser have cached the contents of the popup window? -- Wendy Smoak --------------------------------------------------------------------- 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]
