Page Flow Control container doesn't invoke "beginContext" during the JPF
onDestroy event
----------------------------------------------------------------------------------------
Key: BEEHIVE-1094
URL: http://issues.apache.org/jira/browse/BEEHIVE-1094
Project: Beehive
Type: Bug
Components: NetUI
Versions: V1, 1.0.1
Reporter: Eddie O'Neil
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.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
