I'm not certain how WebSphere implements persistent sessions. Some application servers (I believe including JBoss), just periodically serialize the entire HttpSession for replication purposes. This is really how replication should work, in my opinion.
Others, such as WebLogic, hook HttpSession.setAttribute (), so that data replication only occurs when an attribute is set or changed. This is less intuitive, and more suited to session attributes that are simple and immutable. Tapestry only uses a single HttpSession attribute, but its value is extremely complex and mutable. Hm. Puzzling. I just looked at the code and its no longer conditional, Tapestry will execute HttpSession.setAttribute() at the end of each request cycle. Perhaps your subclass of AbstractEngine is not returning the correct value from isStateful()? -- [EMAIL PROTECTED] http://tapestry.sf.net > > Websphere 3.5.3. Using persistent sessions. > > > > > > hlship@attbi. > > com To: [EMAIL PROTECTED] > > cc: > > 07/22/2002 Subject: Re: [Tapestry-developer] > Visit problem after submit > 09:17 AM > > > > > > > > > What environment are you using? Is clustering enabled? > > -- > [EMAIL PROTECTED] > > http://tapestry.sf.net > > Did anyone ever get a resolution for this? We are having intermittent > > behavior of this kind in a clustered environment. We have a lot of other > > stuff going on, so we are not convinced it has anything to do w/ > Tapestry, > > but this caught my attention. > > > > > > ----- Forwarded by Christian Hall/Technology/Equifax on 07/22/2002 08:34 > AM > > ----- > > |--------+----------------------------------------------> > > | | "Franky Niagara" <[EMAIL PROTECTED]> | > > | | Sent by: | > > | | [EMAIL PROTECTED]| > > | | eforge.net | > > | | | > > | | | > > | | 07/01/2002 06:20 AM | > > | | | > > |--------+----------------------------------------------> > > > > > > -------------------------------------------------------------------------------> > > ------------------| > > | > > > | > > | To: <[EMAIL PROTECTED]> > > > | > > | cc: > > > | > > | Subject: [Tapestry-developer] Visit problem after submit > > > | > > | > > > | > > > > > > ------------------------------------------------------------------------------- > > > ------------------| > > > > > > > > It seems that sometimes after submitting a form all fields in the visit > > object becomes null... > > > > > > I mean in the form listeners we have the visit object with null fields. > > > > > > Why can this happen? > > > > > > > > > > Protect yourself against identity theft with Equifax Credit Watch. Visit > > http://www.creditalert.equifax.com. > > > > This message contains information from Equifax Inc. which may be > > confidential and privileged. If you are not an intended recipient, > please > > refrain from any disclosure, copying, distribution or use of this > > information and note that such actions are prohibited. If you have > > received this transmission in error, please notify by e-mail > > [EMAIL PROTECTED] > > > > > > > > ------------------------------------------------------- > > This sf.net email is sponsored by:ThinkGeek > > Welcome to geek heaven. > > http://thinkgeek.com/sf > > _______________________________________________ > > Tapestry-developer mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/tapestry-developer > > > > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
