You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@beehive.apache.org by "Rich Feit (JIRA)" <be...@incubator.apache.org> on 2005/02/17 22:05:49 UTC

[jira] Resolved: (BEEHIVE-311) return-to='currentPage' doesn't do anything when their isn't a current page in the pageflow

     [ 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