You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by "Alejandro Ramirez (JIRA)" <be...@incubator.apache.org> on 2005/03/26 16:06:24 UTC
[jira] Created: (BEEHIVE-465) PageFlows that do not use annotations to declare SharedFlows should not compile
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
Assigned to: Rich Feit
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 = {@Jpf.Forward(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
[jira] Resolved: (BEEHIVE-465) PageFlows that do not use annotations to declare SharedFlows should not compile
Posted by "Rich Feit (JIRA)" <be...@incubator.apache.org>.
[ 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 = {@Jpf.Forward(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
[jira] Assigned: (BEEHIVE-465) PageFlows that do not use annotations to declare SharedFlows should not compile
Posted by "Rich Feit (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-465?page=history ]
Rich Feit reassigned BEEHIVE-465:
---------------------------------
Assign To: Alejandro Ramirez (was: Rich Feit)
> 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: Alejandro Ramirez
> 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 = {@Jpf.Forward(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
[jira] Updated: (BEEHIVE-465) PageFlows that do not use annotations to declare SharedFlows should not compile
Posted by "Alejandro Ramirez (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-465?page=history ]
Alejandro Ramirez updated BEEHIVE-465:
--------------------------------------
Attachment: SF_ImplicitReferences.zip
> 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
> 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 = {@Jpf.Forward(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
[jira] Closed: (BEEHIVE-465) PageFlows that do not use annotations to declare SharedFlows should not compile
Posted by "Alejandro Ramirez (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-465?page=all ]
Alejandro Ramirez closed BEEHIVE-465:
-------------------------------------
Verified fixed. I now get a warning when compiling the attached pageflow.
> 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: Alejandro Ramirez
> 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 = {@Jpf.Forward(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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (BEEHIVE-465) PageFlows that do not use annotations to declare SharedFlows should not compile
Posted by "Steve Tocco (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-465?page=history ]
Steve Tocco updated BEEHIVE-465:
--------------------------------
Fix Version: V1
moving to v1 (if not needed for ship, please move to Fix For = TBD)
> 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 = {@Jpf.Forward(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