Hi,
I think the problem is that I use the @SessionState in a injected service. And the service being a singleton, explains the behaviour. I guess @SessionState can only be used in pages and components? Have to test this though. On 17/06/13 13:05, Kristian Marinkovic wrote: can you post some code? the page with the annotated field and the methods that manipulate that fields?On Mon, Jun 17, 2013 at 10: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 |
- Sessions getting mixed up Nathan Quirynen
- Re: Sessions getting mixed up Kristian Marinkovic
- Re: Sessions getting mixed up Nathan Quirynen
- Re: Sessions getting mixed up Nathan Quirynen
- Re: Sessions getting mixed up Thiago H. de Paula Figueiredo
- Re: Sessions getting mixed ... Michael Gentry
- Re: Sessions getting m... Thiago H. de Paula Figueiredo
- Re: Sessions getting m... mailingl...@j-b-s.de
- Re: Sessions getti... Howard Lewis Ship
- Re: Sessions getting mixed up Thiago H. de Paula Figueiredo