[ http://issues.apache.org/jira/browse/BEEHIVE-465?page=history ]
Rich Feit resolved BEEHIVE-465:
-------------------------------
Resolution: Fixed
I couldn't make this an error, since the user may have intended to have a
shared flow field that will be manually initialized, but I did add a warning
for this (revision 161160).
> PageFlows that do not use annotations to declare SharedFlows should not
> compile
> -------------------------------------------------------------------------------
>
> Key: BEEHIVE-465
> URL: http://issues.apache.org/jira/browse/BEEHIVE-465
> Project: Beehive
> Type: Bug
> Components: NetUI
> Versions: V1
> Reporter: Alejandro Ramirez
> Assignee: Rich Feit
> Fix For: V1
> Attachments: SF_ImplicitReferences.zip
>
> The attached pageflow should not compile since it is using sharedflows
> without having declared them via annotations:
> @Jpf.Controller()
> public class Controller extends PageFlowController
> {
> private SF_ImplicitReferences.SharedFlow sfRef;
> @Jpf.Action(forwards = [EMAIL PROTECTED](name= "success",
> navigateTo=Jpf.NavigateTo.currentPage)}
> )
> protected Forward getShared() {
> Forward forward = new Forward("success");
> return new Forward( "success", "message", sfRef.getSharedMessage());
> }
> REPRO:
> 1.- Compile the attached pageflow.
> Expected: The pageflow should not compile, and the compiler should throw a
> meaningful message.
> Actual: The pageflow is compiled. However, when you try to access a
> property in the sharedflow using an netui:anchor tag, the user gets a null
> pointer exception (Since the sharedflow is not in the session).
--
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
