[
https://issues.apache.org/jira/browse/BEEHIVE-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carlin Rogers resolved BEEHIVE-1094.
------------------------------------
Resolution: Fixed
Fix Version/s: V.Next
Assignee: Carlin Rogers
This is resolved with SVN revision 611336.
Made changes so that the Control container is initialized correctly for the
page flow's onDestroy() method when navigating away from one page flow to
another page flow.
It corrects some earlier work to manage scoped requests properly. Also, the fix
includes supporting the contextual service for getting the servlet response as
well as the request.
I also updated the PageFlowBeanContext test case so that the controller's
onDestroy() executes the check on the control. Test passes.
As noted in the bug and dev alias, this does not handle the scenario for
onDestroy() being called on an expired session (session time out) when there is
no request object available. In this case there's no way to correctly
initialize the Control container. A developer should check for this case in the
page flow controller's onDestroy().
> Page Flow Control container doesn't invoke "beginContext" during the JPF
> onDestroy event
> ----------------------------------------------------------------------------------------
>
> Key: BEEHIVE-1094
> URL: https://issues.apache.org/jira/browse/BEEHIVE-1094
> Project: Beehive
> Issue Type: Bug
> Components: NetUI
> Affects Versions: 1.0, 1.0.1
> Reporter: Eddie O'Neil
> Assignee: Carlin Rogers
> Fix For: V.Next
>
>
> The Page Flow + Controls integration has a bug where the Control container is
> not initialized during the Page Flow's "onDestroy" method. This happens when
> a JPF is unbound from the session when navigating away from the current flow.
> So, this scenario:
> /foo/Controller.java [has @Controls used in the onDestroy event]
> navigate to:
> /bar/Controller.java
> causes the onDestroy method of the /foo/Controller.java file to be invoked,
> but /foo/Controller.java's PageFlowBeanContext object has not been
> initialized when this happens. The result is that any services available via
> the context may not be initialized. This can be observed in the
> PageFlowControlBeanContext test by uncommenting the "check()" method in the
> JPF's onDestroy lifecycle method. To see the bug, do:
> /controls/pfbeancontext/begin.do
> and then:
> /begin.do
> which should display a stack trace thrown from the control's onAcquire method
> because the contextual service for the PageFlowController can not be found.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
