You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Vjeran Marcinko (JIRA)" <ta...@jakarta.apache.org> on 2004/12/07 14:20:09 UTC
[jira] Created: (TAPESTRY-237) Support for log out action
Support for log out action
--------------------------
Key: TAPESTRY-237
URL: http://nagoya.apache.org/jira/browse/TAPESTRY-237
Project: Tapestry
Type: Improvement
Versions: 3.1
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://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
[jira] Resolved: (TAPESTRY-237) Support for log out action
Posted by "Jesse Kuhnert (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-237?page=all ]
Jesse Kuhnert resolved TAPESTRY-237.
------------------------------------
Fix Version/s: 4.1.1
Resolution: Won't Fix
Assignee: Jesse Kuhnert
Unless I'm reading incorrectly it seems like these problems have mostly gone away as per http://wiki.apache.org/tapestry/LogoutLinkTap4 .
If not I'll re-open.
> Support for log out action
> --------------------------
>
> Key: TAPESTRY-237
> URL: http://issues.apache.org/jira/browse/TAPESTRY-237
> Project: Tapestry
> Issue Type: Improvement
> Components: Framework
> Affects Versions: 4.0
> Reporter: Vjeran Marcinko
> Assigned To: Jesse Kuhnert
> Fix For: 4.1.1
>
>
> 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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Commented: (TAPESTRY-237) Support for log out action
Posted by "Konstantin Ignatyev (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-237?page=comments#action_62902 ]
Konstantin Ignatyev commented on TAPESTRY-237:
----------------------------------------------
I would say there is 3rd way and it works well for me: link to logoff.jsp that looks like this:
<%
session.invalidate();
response.sendRedirect( "app");
%>
Link:
<a href="logoff.jsp" class="menu" jwcid="logoff" >Log Off</a>
Component:
<component id="logoff" type="Any">
<binding name="href" expression="page.engine.contextPath + '/logoff.jsp'"/>
</component>
> Support for log out action
> --------------------------
>
> Key: TAPESTRY-237
> URL: http://issues.apache.org/jira/browse/TAPESTRY-237
> Project: Tapestry
> Type: Improvement
> Versions: 3.1
> 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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
[jira] Updated: (TAPESTRY-237) Support for log out action
Posted by "Brian K. Wallace (JIRA)" <ta...@jakarta.apache.org>.
[ 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: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org