You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@struts.apache.org by Dave Newton <ne...@yahoo.com> on 2007/09/13 17:32:28 UTC
[OT] Re: How to invalidate a session in struts 2.0
--- Gabriel Belingueres <be...@gmail.com> wrote:
> Anyway, I'm still not convinced that invalidating
> the session in the
> action class would yield any more positive results
> than doing it in
> the JSP page.
> Nobody gave any examples, counter-examples or use
> cases that shows it is more convenient to do it in
> the action.
More *convenient*? I don't think the goal was to show
that it was more "convenient" to do it in the action.
The point about keeping code in the code and
presentation in the presentation is the only argument
necessary: when I look for functionality I look in the
code, not the JSP.
I don't have any issues copying a username from a
session user bean into an action property,
particularly since it is likely there is more than a
simple "session.invalidate();" call being made on
logout.
I'd rather keep *all* my logout functionality in one
place and suffer the "overhead" of copying the
username into a property for use on the presentation
side.
d.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org