[jira] Updated: (BEEHIVE-1094) Page Flow Control container doesn't invoke "beginContext" during the JPF onDestroy event

["Carlin Rogers (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/BEEHIVE-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carlin Rogers updated BEEHIVE-1094:
-----------------------------------

    Attachment: jira1094-patch.txt

Here's a patch that will solve this issue for the case where a page flow is destroyed when a user changes from one page flow to another and the current page flow gets removed from the session (destroyed) and replaced by the new page flow.

However, this does not solve the case when the session times out and the "current" page flow is destroyed, via valueUnbound(). In this case there is no request so no way for valid contextual services based on a request.

Anyone have an issue with committing these changes and documenting the issue with a session time out?

> 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
>         Attachments: jira1094-patch.txt
>
>
> 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.