Could Tapestry throw an exception if you use @SessionState in a service? Thanks,
mrg On Mon, Jun 17, 2013 at 9:25 AM, Thiago H. de Paula Figueiredo < thiag...@gmail.com> wrote: > On Mon, Jun 17, 2013 at 8:36 AM, Nathan Quirynen < > nat...@pensionarchitects.be> wrote: > > > Hi, > > > > Hello! > > > > > > 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. > > > > @SessionState is ignored in services. It's meant to be used only in pages, > components and mixins i.e. classes that are transformed by Tapestry. As you > already said, if you want to deal with the session in a service, use > ApplicationStateManager instead. > > Thiago >
