[ http://issues.apache.org/jira/browse/TAPESTRY-237?page=all ]
Brian K. Wallace updated TAPESTRY-237:
--------------------------------------
Component: Framework
> Support for log out action
> --------------------------
>
> Key: TAPESTRY-237
> URL: http://issues.apache.org/jira/browse/TAPESTRY-237
> Project: Tapestry
> Type: Improvement
> Components: Framework
> Versions: 4.0
> Reporter: Vjeran Marcinko
>
> Tapestry lacks good support for quite commonly needed log out action.
> As described here :
> http://wiki.apache.org/jakarta-tapestry/FrequentlyAskedQuestions/LogoutLink
> there are currently 2 ways to achieve logging out - utilizing RestartService,
> or hacking inside Listener methods. Neither is sufficient - shortcomings of
> RestartService and ServiceLink are described, and listener method way is a
> hack utilizing some pieces of code that should normally be hidden from user.
> Let alone mentioning that later case doesn't work always - application can
> get into some strange states raising
> java.lang.IllegalStateException: Session already invalidated
> exceptions.
> It should be great if there was something easily accessible and intuitive as
> IEngine.restart() to be used for this purpose.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
