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/02/03 00:17:17 UTC

[jira] Created: (BEEHIVE-236) actions that contain forms are not valid actions when they are inherited from a sharedflow

actions that contain forms are not valid actions when they are inherited from a sharedflow
------------------------------------------------------------------------------------------

         Key: BEEHIVE-236
         URL: http://issues.apache.org/jira/browse/BEEHIVE-236
     Project: Beehive
        Type: Bug
  Components: NetUI  
    Versions: V1Beta    
 Environment: Tomcat 5.0.0.25, windows xp
    Reporter: Alejandro Ramirez
 Assigned to: Rich Feit 
    Priority: Critical
 Attachments: pageFlows.zip

PRE-CONDIITONS:  You need to configure your container to support login().

1.- Unzip the attached pageflows into a beehive enabled webapp.
2.- Compile and deploy the webapp.
3.- Access the following pageflow: /SharedFlowTest/SharedFlowController.jpf.  In that page, click the link to: "Go to Inheritable SharedFlows".
4.- Now in the inheritable sharedflows page, Click the "Throw failRoles Exception" link.

Expected:  There is an exception that is thrown and caught.  You are sent to the /inheritableSharedFlows/Error.jsp page.  In that page, we have a reference to an inherited action form:
<netui:form action="subSF.goBack">  which is a valid action that should have been inherited by /inheritedSharedFlows/SubSharedFlow.jpfs from /inheritedSharedFlows/SuperSharedFlows/SuperSharedFlow.jpfs.

Actual:  There is an error message letting the user know that the goBack action is not a valid action.
Tag Error
Tag	Form 	Errors	1
Tag Error	Message	Action 'subSF.goBack' is not a valid action.

-- 
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-236) actions that contain forms are not valid actions when they are inherited from a sharedflow

Posted by "Rich Feit (JIRA)" <be...@incubator.apache.org>.
     [ http://issues.apache.org/jira/browse/BEEHIVE-236?page=history ]
     
Rich Feit resolved BEEHIVE-236:
-------------------------------

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

> actions that contain forms are not valid actions when they are inherited from a sharedflow
> ------------------------------------------------------------------------------------------
>
>          Key: BEEHIVE-236
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-236
>      Project: Beehive
>         Type: Bug
>   Components: NetUI
>     Versions: V1Beta
>  Environment: Tomcat 5.0.0.25, windows xp
>     Reporter: Alejandro Ramirez
>     Assignee: Alejandro Ramirez
>     Priority: Critical
>  Attachments: pageFlows.zip
>
> PRE-CONDIITONS:  You need to configure your container to support login().
> 1.- Unzip the attached pageflows into a beehive enabled webapp.
> 2.- Compile and deploy the webapp.
> 3.- Access the following pageflow: /SharedFlowTest/SharedFlowController.jpf.  In that page, click the link to: "Go to Inheritable SharedFlows".
> 4.- Now in the inheritable sharedflows page, Click the "Throw failRoles Exception" link.
> Expected:  There is an exception that is thrown and caught.  You are sent to the /inheritableSharedFlows/Error.jsp page.  In that page, we have a reference to an inherited action form:
> <netui:form action="subSF.goBack">  which is a valid action that should have been inherited by /inheritedSharedFlows/SubSharedFlow.jpfs from /inheritedSharedFlows/SuperSharedFlows/SuperSharedFlow.jpfs.
> Actual:  There is an error message letting the user know that the goBack action is not a valid action.
> Tag Error
> Tag	Form 	Errors	1
> Tag Error	Message	Action 'subSF.goBack' is not a valid action.

-- 
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-236) actions that contain forms are not valid actions when they are inherited from a sharedflow

Posted by "Alejandro Ramirez (JIRA)" <be...@incubator.apache.org>.
     [ http://issues.apache.org/jira/browse/BEEHIVE-236?page=history ]

Alejandro Ramirez updated BEEHIVE-236:
--------------------------------------

    Attachment: pageFlows.zip

Pageflows to reproduce the problem.

> actions that contain forms are not valid actions when they are inherited from a sharedflow
> ------------------------------------------------------------------------------------------
>
>          Key: BEEHIVE-236
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-236
>      Project: Beehive
>         Type: Bug
>   Components: NetUI
>     Versions: V1Beta
>  Environment: Tomcat 5.0.0.25, windows xp
>     Reporter: Alejandro Ramirez
>     Assignee: Rich Feit
>     Priority: Critical
>  Attachments: pageFlows.zip
>
> PRE-CONDIITONS:  You need to configure your container to support login().
> 1.- Unzip the attached pageflows into a beehive enabled webapp.
> 2.- Compile and deploy the webapp.
> 3.- Access the following pageflow: /SharedFlowTest/SharedFlowController.jpf.  In that page, click the link to: "Go to Inheritable SharedFlows".
> 4.- Now in the inheritable sharedflows page, Click the "Throw failRoles Exception" link.
> Expected:  There is an exception that is thrown and caught.  You are sent to the /inheritableSharedFlows/Error.jsp page.  In that page, we have a reference to an inherited action form:
> <netui:form action="subSF.goBack">  which is a valid action that should have been inherited by /inheritedSharedFlows/SubSharedFlow.jpfs from /inheritedSharedFlows/SuperSharedFlows/SuperSharedFlow.jpfs.
> Actual:  There is an error message letting the user know that the goBack action is not a valid action.
> Tag Error
> Tag	Form 	Errors	1
> Tag Error	Message	Action 'subSF.goBack' is not a valid action.

-- 
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-236) actions that contain forms are not valid actions when they are inherited from a sharedflow

Posted by "Rich Feit (JIRA)" <be...@incubator.apache.org>.
     [ http://issues.apache.org/jira/browse/BEEHIVE-236?page=history ]
     
Rich Feit resolved BEEHIVE-236:
-------------------------------

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

inheritableSharedFlows/Error.jsp actually has a typo.  This:
        <netui:form action="subSF.goBack">
should be this:
        <netui:form action="SubSF.goBack">

If it makes you feel better, I got all the way into the debugger before I noticed it.  :)


> actions that contain forms are not valid actions when they are inherited from a sharedflow
> ------------------------------------------------------------------------------------------
>
>          Key: BEEHIVE-236
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-236
>      Project: Beehive
>         Type: Bug
>   Components: NetUI
>     Versions: V1Beta
>  Environment: Tomcat 5.0.0.25, windows xp
>     Reporter: Alejandro Ramirez
>     Assignee: Alejandro Ramirez
>     Priority: Critical
>  Attachments: pageFlows.zip
>
> PRE-CONDIITONS:  You need to configure your container to support login().
> 1.- Unzip the attached pageflows into a beehive enabled webapp.
> 2.- Compile and deploy the webapp.
> 3.- Access the following pageflow: /SharedFlowTest/SharedFlowController.jpf.  In that page, click the link to: "Go to Inheritable SharedFlows".
> 4.- Now in the inheritable sharedflows page, Click the "Throw failRoles Exception" link.
> Expected:  There is an exception that is thrown and caught.  You are sent to the /inheritableSharedFlows/Error.jsp page.  In that page, we have a reference to an inherited action form:
> <netui:form action="subSF.goBack">  which is a valid action that should have been inherited by /inheritedSharedFlows/SubSharedFlow.jpfs from /inheritedSharedFlows/SuperSharedFlows/SuperSharedFlow.jpfs.
> Actual:  There is an error message letting the user know that the goBack action is not a valid action.
> Tag Error
> Tag	Form 	Errors	1
> Tag Error	Message	Action 'subSF.goBack' is not a valid action.

-- 
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] Reopened: (BEEHIVE-236) actions that contain forms are not valid actions when they are inherited from a sharedflow

Posted by "Rich Feit (JIRA)" <be...@incubator.apache.org>.
     [ http://issues.apache.org/jira/browse/BEEHIVE-236?page=history ]
     
Rich Feit reopened BEEHIVE-236:
-------------------------------

     Assign To: Rich Feit  (was: Alejandro Ramirez)

Wrong resolution here...


> actions that contain forms are not valid actions when they are inherited from a sharedflow
> ------------------------------------------------------------------------------------------
>
>          Key: BEEHIVE-236
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-236
>      Project: Beehive
>         Type: Bug
>   Components: NetUI
>     Versions: V1Beta
>  Environment: Tomcat 5.0.0.25, windows xp
>     Reporter: Alejandro Ramirez
>     Assignee: Rich Feit
>     Priority: Critical
>  Attachments: pageFlows.zip
>
> PRE-CONDIITONS:  You need to configure your container to support login().
> 1.- Unzip the attached pageflows into a beehive enabled webapp.
> 2.- Compile and deploy the webapp.
> 3.- Access the following pageflow: /SharedFlowTest/SharedFlowController.jpf.  In that page, click the link to: "Go to Inheritable SharedFlows".
> 4.- Now in the inheritable sharedflows page, Click the "Throw failRoles Exception" link.
> Expected:  There is an exception that is thrown and caught.  You are sent to the /inheritableSharedFlows/Error.jsp page.  In that page, we have a reference to an inherited action form:
> <netui:form action="subSF.goBack">  which is a valid action that should have been inherited by /inheritedSharedFlows/SubSharedFlow.jpfs from /inheritedSharedFlows/SuperSharedFlows/SuperSharedFlow.jpfs.
> Actual:  There is an error message letting the user know that the goBack action is not a valid action.
> Tag Error
> Tag	Form 	Errors	1
> Tag Error	Message	Action 'subSF.goBack' is not a valid action.

-- 
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-236) actions that contain forms are not valid actions when they are inherited from a sharedflow

Posted by "Alejandro Ramirez (JIRA)" <be...@incubator.apache.org>.
     [ http://issues.apache.org/jira/browse/BEEHIVE-236?page=history ]
     
Alejandro Ramirez closed BEEHIVE-236:
-------------------------------------


Verified as invalid.  I fixed inheritableSharedFlows/Error.jsp as follows:
From:
        <netui:form action="subSF.goBack">
To:
        <netui:form action="SubSF.goBack"> 
and that worked.

> actions that contain forms are not valid actions when they are inherited from a sharedflow
> ------------------------------------------------------------------------------------------
>
>          Key: BEEHIVE-236
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-236
>      Project: Beehive
>         Type: Bug
>   Components: NetUI
>     Versions: V1Beta
>  Environment: Tomcat 5.0.0.25, windows xp
>     Reporter: Alejandro Ramirez
>     Assignee: Alejandro Ramirez
>     Priority: Critical
>  Attachments: pageFlows.zip
>
> PRE-CONDIITONS:  You need to configure your container to support login().
> 1.- Unzip the attached pageflows into a beehive enabled webapp.
> 2.- Compile and deploy the webapp.
> 3.- Access the following pageflow: /SharedFlowTest/SharedFlowController.jpf.  In that page, click the link to: "Go to Inheritable SharedFlows".
> 4.- Now in the inheritable sharedflows page, Click the "Throw failRoles Exception" link.
> Expected:  There is an exception that is thrown and caught.  You are sent to the /inheritableSharedFlows/Error.jsp page.  In that page, we have a reference to an inherited action form:
> <netui:form action="subSF.goBack">  which is a valid action that should have been inherited by /inheritedSharedFlows/SubSharedFlow.jpfs from /inheritedSharedFlows/SuperSharedFlows/SuperSharedFlow.jpfs.
> Actual:  There is an error message letting the user know that the goBack action is not a valid action.
> Tag Error
> Tag	Form 	Errors	1
> Tag Error	Message	Action 'subSF.goBack' is not a valid action.

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