[ 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
