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

["Rich Feit (JIRA)" <de...@beehive.apache.org>]

    [ http://issues.apache.org/jira/browse/BEEHIVE-1003?page=comments#action_12357663 ] 

Rich Feit commented on BEEHIVE-1003:
------------------------------------

I just commented on this in the dev@beehive thread.  I'm suggesting we replace the reflection-based method invocation with a call to PageFlowUtils.strutsLookup().  Will that work to fix this particular issue?

> 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: Carlin Rogers
>      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