[ http://issues.apache.org/jira/browse/BEEHIVE-325?page=history ]
Rich Feit resolved BEEHIVE-325:
-------------------------------
Assign To: Nathan Jantz (was: Rich Feit)
Resolution: Fixed
Fixed with revision 154219. Turns out that our Servlet Filter was bailing out
because the request URI didn't end in any appropriate extension (the request
URI was something like this: /myWebapp/foo/). I switched it to use the Servlet
path, which is always something like /foo/index.jsp.
> 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
