I've never heard of that? I suspect that this is due to the fact that the T5 page pool is forgotten and @Retain is used or something similar?
Page cannot contain ANY instance variables, excluding the ones that are same regardless of the session (user) accessing the page or maintained by T5. Same applies to components. Also instance variables are cleaned if not marked with @Retain when page is returned to page pool. - Ville toby78 wrote: > > I have heard there are some issues with "Session bleedings" in Tapestry5. > > Will those issues be fixed by November? > > I would like to go live with a T5 application by November/December.... > > Thanks! > > Tobias > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Access-to-HttpSessions-tp20051371p20067243.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
