[ http://issues.apache.org/jira/browse/BEEHIVE-427?page=history ]
     
Rich Feit resolved BEEHIVE-427:
-------------------------------

     Assign To: Alejandro Ramirez  (was: Rich Feit)
    Resolution: Invalid

I misunderstood this the first time I looked at it (well, maybe I'm still 
misunderstanding :)).  This seems like it's working correctly to me.  
Controller.jpf *isn't* getting any sort of automatic reference to the shared 
flow.  The nested page flow is passing back a form bean, and that form bean 
happens to be an instance of a static inner class of the shared flow, but 
that's fine.  It's the same as using any other static inner class.

If I'm missing the point of this, feel free to reopen.

> appbash031005 Users should not be able to use sharedflows within a pageflow 
> without having declared them before
> ---------------------------------------------------------------------------------------------------------------
>
>          Key: BEEHIVE-427
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-427
>      Project: Beehive
>         Type: Bug
>   Components: NetUI
>     Versions: V1Beta
>     Reporter: Alejandro Ramirez
>     Assignee: Alejandro Ramirez
>      Fix For: V1
>  Attachments: nestedSharedFlowsTest.zip
>
> Using the attached pageflows, deploy them to an existing beehive enabled 
> webapp.
> 1.- The pageflow "nestedSharedFlow.Controller" has the following forward: 
>     @Jpf.Action(forwards = {
>         @Jpf.Forward(name = "results",
>                      path = "results.jsp")
>     })
>     protected Forward chooseAirportDone( 
> chooseAirport.NestedSharedFlowTest.ResultsForm form )
>     {
>         _chosenAirport = form.getAirport();
>         return new Forward( "results" );
>     }
> However, it does not include a SharedFlow declaration.  
> Expected: a compiler error letting the user know that the pageflow needs to 
> the declare the use of a sharedflow.
> Actual: The pageflow actually works.  However, I think it only works because 
> the nested pageflow "chooseAirport.chooseAirportController" gets executed 
> first and that puts the sharedflow "chooseAirport.NestedSharedFlowTest" into 
> the session.  That same sharedflow is later on used by 
> "nestedSharedFlow.Controller" as described in step 1.

-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

Reply via email to