You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by "Karen Stutesman (JIRA)" <be...@incubator.apache.org> on 2005/02/17 01:08:48 UTC
[jira] Created: (BEEHIVE-311) Tree: Error on return to current page after a session timeout
Tree: Error on return to current page after a session timeout
-------------------------------------------------------------
Key: BEEHIVE-311
URL: http://issues.apache.org/jira/browse/BEEHIVE-311
Project: Beehive
Type: Improvement
Components: NetUI
Versions: V1
Reporter: Karen Stutesman
There are a few cases such as a session timeout where a user might unknowingly expect a tree to be present but receives a message: "You have tried to return to a recent page in the current page flow through return-to='currentPage', but there is no appropriate page".
Is there a way the tree could rebuild somehow in these cases instead of receiving this error message?
--
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
[jira] Closed: (BEEHIVE-311) return-to='currentPage' doesn't do anything when their isn't a current page in the pageflow
Posted by "Krista Baker (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-311?page=all ]
Krista Baker closed BEEHIVE-311:
--------------------------------
Verified that the session-expired exception can be caught and the user can be directed to another method or page when the current page is navigated to, but it doesn't exist yet.
> return-to='currentPage' doesn't do anything when their isn't a current page in the pageflow
> -------------------------------------------------------------------------------------------
>
> Key: BEEHIVE-311
> URL: http://issues.apache.org/jira/browse/BEEHIVE-311
> Project: Beehive
> Type: Improvement
> Components: NetUI
> Versions: V1
> Reporter: Karen Stutesman
> Assignee: Krista Baker
> Fix For: V1Beta
>
> There are a few cases such as a session timeout where a user might unknowingly expect a tree to be present but receives a message: "You have tried to return to a recent page in the current page flow through return-to='currentPage', but there is no appropriate page".
> Is there a way the tree could rebuild somehow in these cases instead of receiving this error message?
--
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
[jira] Assigned: (BEEHIVE-311) return-to='currentPage' doesn't do anything when their isn't a current page in the pageflow
Posted by "Karen Stutesman (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-311?page=history ]
Karen Stutesman reassigned BEEHIVE-311:
---------------------------------------
Assign To: Krista Baker (was: Karen Stutesman)
> return-to='currentPage' doesn't do anything when their isn't a current page in the pageflow
> -------------------------------------------------------------------------------------------
>
> Key: BEEHIVE-311
> URL: http://issues.apache.org/jira/browse/BEEHIVE-311
> Project: Beehive
> Type: Improvement
> Components: NetUI
> Versions: V1
> Reporter: Karen Stutesman
> Assignee: Krista Baker
> Fix For: V1Beta
>
> There are a few cases such as a session timeout where a user might unknowingly expect a tree to be present but receives a message: "You have tried to return to a recent page in the current page flow through return-to='currentPage', but there is no appropriate page".
> Is there a way the tree could rebuild somehow in these cases instead of receiving this error message?
--
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
[jira] Updated: (BEEHIVE-311) return-to='currentPage' doesn't do anything when their isn't a current page in the pageflow
Posted by "Daryl Olander (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-311?page=history ]
Daryl Olander updated BEEHIVE-311:
----------------------------------
Summary: return-to='currentPage' doesn't do anything when their isn't a current page in the pageflow (was: Tree: Error on return to current page after a session timeout)
Rich, this is the general problem that when you call an action on a page flow that has return-to='currentPage', and there isn't a current page, you get this message. This happens pretty frequently in testing the tree. Other places this may occur is if you bookmark an action in a pageflow that returns to the current page.
Not sure what we should do about it, perhaps we should put up some type of error page that gives a link to the begin action and explains the problem. Perhaps we should just go directly to being?
I'm not sure if I ever entered this, but Karen entered it in Jira because I'm pretty sure it wasn't there.
> return-to='currentPage' doesn't do anything when their isn't a current page in the pageflow
> -------------------------------------------------------------------------------------------
>
> Key: BEEHIVE-311
> URL: http://issues.apache.org/jira/browse/BEEHIVE-311
> Project: Beehive
> Type: Improvement
> Components: NetUI
> Versions: V1
> Reporter: Karen Stutesman
> Assignee: Rich Feit
>
> There are a few cases such as a session timeout where a user might unknowingly expect a tree to be present but receives a message: "You have tried to return to a recent page in the current page flow through return-to='currentPage', but there is no appropriate page".
> Is there a way the tree could rebuild somehow in these cases instead of receiving this error message?
--
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
[jira] Updated: (BEEHIVE-311) return-to='currentPage' doesn't do anything when their isn't a current page in the pageflow
Posted by "Rich Feit (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-311?page=history ]
Rich Feit updated BEEHIVE-311:
------------------------------
Assign To: Alejandro Ramirez (was: Rich Feit)
> return-to='currentPage' doesn't do anything when their isn't a current page in the pageflow
> -------------------------------------------------------------------------------------------
>
> Key: BEEHIVE-311
> URL: http://issues.apache.org/jira/browse/BEEHIVE-311
> Project: Beehive
> Type: Improvement
> Components: NetUI
> Versions: V1
> Reporter: Karen Stutesman
> Assignee: Alejandro Ramirez
> Fix For: V1Beta
>
> There are a few cases such as a session timeout where a user might unknowingly expect a tree to be present but receives a message: "You have tried to return to a recent page in the current page flow through return-to='currentPage', but there is no appropriate page".
> Is there a way the tree could rebuild somehow in these cases instead of receiving this error message?
--
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
[jira] Assigned: (BEEHIVE-311) return-to='currentPage' doesn't do anything when their isn't a current page in the pageflow
Posted by "Alejandro Ramirez (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-311?page=history ]
Alejandro Ramirez reassigned BEEHIVE-311:
-----------------------------------------
Assign To: Karen Stutesman (was: Alejandro Ramirez)
Please Verify and Close.
> return-to='currentPage' doesn't do anything when their isn't a current page in the pageflow
> -------------------------------------------------------------------------------------------
>
> Key: BEEHIVE-311
> URL: http://issues.apache.org/jira/browse/BEEHIVE-311
> Project: Beehive
> Type: Improvement
> Components: NetUI
> Versions: V1
> Reporter: Karen Stutesman
> Assignee: Karen Stutesman
> Fix For: V1Beta
>
> There are a few cases such as a session timeout where a user might unknowingly expect a tree to be present but receives a message: "You have tried to return to a recent page in the current page flow through return-to='currentPage', but there is no appropriate page".
> Is there a way the tree could rebuild somehow in these cases instead of receiving this error message?
--
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
[jira] Commented: (BEEHIVE-311) return-to='currentPage' doesn't do anything when their isn't a current page in the pageflow
Posted by "John Rohrlich (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-311?page=comments#action_59332 ]
John Rohrlich commented on BEEHIVE-311:
---------------------------------------
If we can detect the cause (session timeout, calling an action in the middle of a page flow rather than starting with begin, etc.) let's put up an error page with the reason. Otherwise I think an error page with a list of possible reasons.
> return-to='currentPage' doesn't do anything when their isn't a current page in the pageflow
> -------------------------------------------------------------------------------------------
>
> Key: BEEHIVE-311
> URL: http://issues.apache.org/jira/browse/BEEHIVE-311
> Project: Beehive
> Type: Improvement
> Components: NetUI
> Versions: V1
> Reporter: Karen Stutesman
> Assignee: Rich Feit
>
> There are a few cases such as a session timeout where a user might unknowingly expect a tree to be present but receives a message: "You have tried to return to a recent page in the current page flow through return-to='currentPage', but there is no appropriate page".
> Is there a way the tree could rebuild somehow in these cases instead of receiving this error message?
--
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
[jira] Resolved: (BEEHIVE-311) return-to='currentPage' doesn't do anything when their isn't a current page in the pageflow
Posted by "Rich Feit (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-311?page=history ]
Rich Feit resolved BEEHIVE-311:
-------------------------------
Resolution: Fixed
Fix Version: V1Beta
Fixed with revision 154180 -- the default for throw-session-expired-exception is now truly true.
Note that the SessionExpiredException needs to be handled in a @Jpf.Catch, somewhere. I'm not sure what else we can do beyond providing the information and a way to handle it. If you think of something, just reopen the issue.
> return-to='currentPage' doesn't do anything when their isn't a current page in the pageflow
> -------------------------------------------------------------------------------------------
>
> Key: BEEHIVE-311
> URL: http://issues.apache.org/jira/browse/BEEHIVE-311
> Project: Beehive
> Type: Improvement
> Components: NetUI
> Versions: V1
> Reporter: Karen Stutesman
> Assignee: Rich Feit
> Fix For: V1Beta
>
> There are a few cases such as a session timeout where a user might unknowingly expect a tree to be present but receives a message: "You have tried to return to a recent page in the current page flow through return-to='currentPage', but there is no appropriate page".
> Is there a way the tree could rebuild somehow in these cases instead of receiving this error message?
--
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
[jira] Commented: (BEEHIVE-311) return-to='currentPage' doesn't do anything when their isn't a current page in the pageflow
Posted by "Rich Feit (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-311?page=comments#action_59341 ]
Rich Feit commented on BEEHIVE-311:
-----------------------------------
If you have the <pageflow-config><throw-session-expired-exception> element set to true in netui-config.xml (true is the default), you *should* be getting a SessionExpiredException. We throw this when we have a condition ("no previous page" in your case) that's likely to have been caused by session expiration. You can handle this exception using @Jpf.Catch to do whatever you want (go to an error page, run the begin action, etc.).
@Jpf.Controller(
catches={
@Jpf.Catch(type=SessionExpiredException.class, path="error.jsp")
}
)
or
@Jpf.Controller(
catches={
@Jpf.Catch(type=SessionExpiredException.class, method="mySessionExceptionHandler")
}
)
I am not currently reading the default value correctly, however, so if this element (throw-session-expired-exception) isn't present, you'll get a NoPreviousPageException. I'm working on a fix for that now.
> return-to='currentPage' doesn't do anything when their isn't a current page in the pageflow
> -------------------------------------------------------------------------------------------
>
> Key: BEEHIVE-311
> URL: http://issues.apache.org/jira/browse/BEEHIVE-311
> Project: Beehive
> Type: Improvement
> Components: NetUI
> Versions: V1
> Reporter: Karen Stutesman
> Assignee: Rich Feit
>
> There are a few cases such as a session timeout where a user might unknowingly expect a tree to be present but receives a message: "You have tried to return to a recent page in the current page flow through return-to='currentPage', but there is no appropriate page".
> Is there a way the tree could rebuild somehow in these cases instead of receiving this error message?
--
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
[jira] Assigned: (BEEHIVE-311) Tree: Error on return to current page after a session timeout
Posted by "Daryl Olander (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-311?page=history ]
Daryl Olander reassigned BEEHIVE-311:
-------------------------------------
Assign To: Rich Feit
> Tree: Error on return to current page after a session timeout
> -------------------------------------------------------------
>
> Key: BEEHIVE-311
> URL: http://issues.apache.org/jira/browse/BEEHIVE-311
> Project: Beehive
> Type: Improvement
> Components: NetUI
> Versions: V1
> Reporter: Karen Stutesman
> Assignee: Rich Feit
>
> There are a few cases such as a session timeout where a user might unknowingly expect a tree to be present but receives a message: "You have tried to return to a recent page in the current page flow through return-to='currentPage', but there is no appropriate page".
> Is there a way the tree could rebuild somehow in these cases instead of receiving this error message?
--
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