beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Ramirez (JIRA)" <beehive-...@incubator.apache.org>
Subject [jira] Assigned: (BEEHIVE-311) return-to='currentPage' doesn't do anything when their isn't a current page in the pageflow
Date Wed, 23 Feb 2005 00:34:56 GMT
     [ 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


Mime
View raw message