beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eddie O'Neil (JIRA)" <...@beehive.apache.org>
Subject [jira] Reopened: (BEEHIVE-1003) Calling FlowControllerFactory.createPageFlow() outside of page flow request processor and page filter does not initialize controls correctly
Date Mon, 14 Nov 2005 21:01:31 GMT
     [ http://issues.apache.org/jira/browse/BEEHIVE-1003?page=all ]
     
Eddie O'Neil reopened BEEHIVE-1003:
-----------------------------------

     Assign To: Carlin Rogers  (was: Alejandro Ramirez)

Reopening this...the problem is that with this initialization process, the ControlContainerContext
only exists during between the initialize and uninitialize calls.  This leads to trouble when
a control implementation depends on the CCC to be available at runtime.  

The basic issue is that the control lifecycle usually works like this:

- initialize
- unit of work (request, method invocation, page rendering)
- uninitialize

but the JavaControlUtils fix does this:

- initialize
- uninitialize 
- unit of work (reflective call)

I've got a control implementation that will demonstrate this problem; should be possible to
basically swap-out the PortfolioControl used in the test to demonstrate this problem.

I'll record a test that ensures that normal JPFs "do the right thing" here and will leave
the fix and test for the FlowControllerFactory to Carlin.

> 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

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