beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julie Zhuo (JIRA)" <...@beehive.apache.org>
Subject [jira] Closed: (BEEHIVE-1003) Calling FlowControllerFactory.createPageFlow() outside of page flow request processor and page filter does not initialize controls correctly
Date Mon, 30 Jan 2006 21:46:35 GMT
     [ http://issues.apache.org/jira/browse/BEEHIVE-1003?page=all ]
     
Julie Zhuo closed BEEHIVE-1003:
-------------------------------


Verified with rev372375.

With the revision  http://svn.apache.org/viewcvs?rev=371706&view=rev,  the CCC initialization
and uninitialization are all handled in the FlowControllerFactory. So, it is no longer needed
for the caller to do any of those. The createPageFlow tests are now producing the same results
whether or not the param is passed in the url which is the correct behavior. Although the
FlowControllerFactory java doc have not been changed back yet. Will open a separate Jira bug
to track on this java doc issue so that we can close this one here.

> 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: Julie Zhuo
>      Fix For: 1.0.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