You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by "Nathan Jantz (JIRA)" <be...@incubator.apache.org> on 2005/02/27 00:45:48 UTC
[jira] Closed: (BEEHIVE-325) A new pageflow instance is not being created when leaving and navigating back to a pageflow
[ http://issues.apache.org/jira/browse/BEEHIVE-325?page=history ]
Nathan Jantz closed BEEHIVE-325:
--------------------------------
This is verified to be working now under Tomcat.
> A new pageflow instance is not being created when leaving and navigating back to a pageflow
> -------------------------------------------------------------------------------------------
>
> Key: BEEHIVE-325
> URL: http://issues.apache.org/jira/browse/BEEHIVE-325
> Project: Beehive
> Type: Bug
> Components: NetUI
> Versions: V1Beta
> Environment: Tested on Windows runnings the usual required java components for Beehive.
> Reporter: Nathan Jantz
> Assignee: Nathan Jantz
>
> A new pageflow instance is not being created when leaving and navigating back to a pageflow through a begin action (in the controller) that forwards to an index.jsp page.
> This is only happening in Tomcat. It appears the Tomcat servlet filter is not being invoked in this scenario which prevents a new pageflow instance from being created. When hitting the index.jsp directly in a URL, the new instance is created as expected.
> This is related to BEEHIVE-245 issue, but I thought I would write up an new issue because this problem was found running an entirely different scenario using pageflow scoping, and users of pageflow scoping may run into this problem.
> I will attach code here shortly.
--
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