A common mistake is to initialize @Persist or @SessionState fields in its declaration (such as @Persist private User user = new User(). Don't do that. Use event handler methods for that. setupRender() is usually a good choice.
On Mon, Jun 17, 2013 at 5:49 AM, Nathan Quirynen < nat...@pensionarchitects.be> wrote: > Hi, > > I'm having some weird issues with sessions that are getting mixed up, for > example: > > I open a page in both Firefox and Safari (so they are a different > HttpSession). > I do something in Firefox that sets a value in an object that is annotated > with @SessionState. > Apparently this change also affected the value in my Safari session. > > What could be affecting this? Could this be a code problem, or maybe a > configuration/Tomcat problem? > I have no idea on where to start searching, so any pointers are welcome! > > Thanks, > Nathan > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > users-unsubscribe@tapestry.**apache.org<users-unsubscr...@tapestry.apache.org> > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Thiago
