beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carlin Rogers (JIRA)" <>
Subject [jira] Commented: (BEEHIVE-1094) Page Flow Control container doesn't invoke "beginContext" during the JPF onDestroy event
Date Thu, 10 Jan 2008 00:13:34 GMT


Carlin Rogers commented on BEEHIVE-1094:

I just removed the patch I attached earlier. It is flawed because it does not manage a scoped
request properly. Also, the patch should be improved to include the response when available
for the destroy (when user changes page flows) and not just the request. Potentially, a control
could try to get a response object from contextual service. Will work on this some more.

> Page Flow Control container doesn't invoke "beginContext" during the JPF onDestroy event
> ----------------------------------------------------------------------------------------
>                 Key: BEEHIVE-1094
>                 URL:
>             Project: Beehive
>          Issue Type: Bug
>          Components: NetUI
>    Affects Versions: 1.0, 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/ [has @Controls used in the onDestroy event]
> navigate to:
>   /bar/ 
> causes the onDestroy method of the /foo/ file to be invoked, but /foo/'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/
> and then:
>   /
> 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.

View raw message