Hi Thiago,
Thanks for the reply, I have modified the code as you sugested, looks neat.
the problem seems having to do with @ApplicationState, I have this for the
same class in two places, also create it in a service, in one page, I have A
@ApplicationState SessionDat _dat, in the same time I call the service
which might also create an instance of SessionDat, I'm still tracing...
thanks,
Angelo
Thiago H. de Paula Figueiredo wrote:
>
> Please post the class that contains the snippet you posted here. By
> the way, you don't need to asm.set(MySession.class, null), as you're
> invalidating the session. You can also inject HttpServletRequest
> directly and instead of getting it from RequestGlobals. Better yet,
> inject Tapestry's Request and do:
>
> Session session = request.getSession(false);
> if (session != null) {
> session.invalidate();
> }
>
> --
> Thiago
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
>
--
View this message in context:
http://www.nabble.com/T5%3ACannot-create-a-session-after-the-response-has-been-committed-tp22099641p22102555.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
