Re: Sessions getting mixed up

Nathan Quirynen Mon, 17 Jun 2013 06:20:04 -0700

I made the mistake of using @SessionState in a service, while this is only supported in pages components or mixins.
So the annotation didn't do anything. So there was always just one instantiation of the object, which everyone used.

I fixed my problem by using ApplicationStateManager in this service instead.

On 17/06/13 13:36, Nathan Quirynen wrote:

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
--

Een klare kijk op aanvullende pensioenen

Nathan Quirynen
03 340 04 60 | 0494 28 45 15
nat...@pensionarchitects.be

Follow us on Web | Twitter | LinkedIn | RSS | YouTube

Re: Sessions getting mixed up

Reply via email to