> you don't need to asm.set(MySession.class, null), as you're
> invalidating the session.
True, but I suggest you do it anyway, even if just as a safety net, I have
encountered some strange things so it cant hurt.
----- Original Message -----
From: "Thiago H. de Paula Figueiredo" <thiag...@gmail.com>
To: "Tapestry users" <users@tapestry.apache.org>
Sent: Thursday, 19 February, 2009 15:20:07 GMT +02:00 Athens, Beirut,
Bucharest, Istanbul
Subject: Re: T5:Cannot create a session after the response has been committed
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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
