[ 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
