[jira] Resolved: (BEEHIVE-1003) Calling FlowControllerFactory.createPageFlow() outside of page flow request processor and page filter does not initialize controls correctly

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

     [ http://issues.apache.org/jira/browse/BEEHIVE-1003?page=all ]
     
Carlin Rogers resolved BEEHIVE-1003:
------------------------------------

    Resolution: Fixed
     Assign To: Alejandro Ramirez  (was: Carlin Rogers)

Fixed with revision 332482.

I modified JavaControlUtils.initJavaControls() such that if the call to getControlBeanContext() returns null we call initializeControlContext() and try to get the control bean context again. In this ase we will also call uninitializeControlContext().

This revision includes a servlet that calls FlowControllerFactory method, createPageFlow(), then checks to see that the control was initialized. There is a new TestRecorder file as well.

To reproduce the error condition, build and run the test files in a workspace that does not have the changes to JavaControlUtils.

> Calling FlowControllerFactory.createPageFlow() outside of page flow request processor and page filter does not initialize controls correctly
> --------------------------------------------------------------------------------------------------------------------------------------------
>
>          Key: BEEHIVE-1003
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-1003
>      Project: Beehive
>         Type: Bug
>   Components: NetUI
>     Versions: V1
>     Reporter: Carlin Rogers
>     Assignee: Alejandro Ramirez
>      Fix For: 1.1

>
> Calling the FlowControllerFactory method createPageFlow() outside of the page flow request processor and page filter does not initialize controls correctly. The page flow request processor and/or the page filter call JavaControlUtils.initializeControlContext() to create a ControlBeanContext. However, the direct call to createPageFlow() method, eventualy drills down to JavaControlUtils.initJavaControls(), but the ControlBeanContext is null and with asserts on, this method fails. With asserts off, the method continues but the control in the page flow will not have been initialized.

-- 
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