beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carlin Rogers (JIRA)" <...@beehive.apache.org>
Subject [jira] Resolved: (BEEHIVE-1003) Calling FlowControllerFactory.createPageFlow() outside of page flow request processor and page filter does not initialize controls correctly
Date Thu, 17 Nov 2005 01:43:29 GMT
     [ 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 345162.

The fix in this revision just adds Javadoc to both the FlowControllerFactory and the JavaControlUtils
classes that before creating a FlowController via the factory, the caller should first initialize
the ControlContainerContext, then after once the FlowController has gone through its life
cylce, the caller should uninitialize the ControlContainerContext.
See the dev list discussion, http://www.mail-archive.com/dev@beehive.apache.org/msg01359.html.

The test has been updated to do the CCC initialize/uninitialize around the calls to create
the FlowController as well as execute the begin action.

Note that the control used in this test includes the same implementation as Eddie's control
to depends on the CCC to be available at runtime.

To run the test manually and see the failures when the initialization is not done around the
FCF, just hit the servlet... /createPageFlow/. note that the control has logging in it so
you log4j.xml can be tuned accordingly for more detail.

To run the test successfully, use the query, initializeControlContext=true...
(e.g. /coreWeb/createPageFlow/?initializeControlContext=true)

> 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
>  Attachments: pfControlLifecycle.jar
>
> 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


Mime
View raw message