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/17 20:05:48 UTC
[jira] Created: (BEEHIVE-323) It would be great to have two additional methods in PageFlowController to get and remove sharedflows.
It would be great to have two additional methods in PageFlowController to get and remove sharedflows.
-----------------------------------------------------------------------------------------------------
Key: BEEHIVE-323
URL: http://issues.apache.org/jira/browse/BEEHIVE-323
Project: Beehive
Type: Improvement
Components: NetUI
Versions: V1Beta
Reporter: Alejandro Ramirez
Assigned to: Rich Feit
Priority: Critical
Currently, we have two methods in org.apache.beehive.netui.pageflow.PageFlowUtils
to get and remove sharedflows.
1.- public static SharedFlowController getSharedFlow( String sharedFlowClassName, HttpServletRequest request )
2.- public static void removeSharedFlow( String sharedFlowClassName, HttpServletRequest request )
It would be great to have similar functionality under: org.apache.beehive.netui.pageflow.PageFlowController
1.- public static SharedFlowController getSharedFlow( String sharedFlowClassName)
2.- public static void removeSharedFlow( String sharedFlowClassName)
--
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-323) It would be great to have two additional methods in PageFlowController to get and remove sharedflows.
Posted by "Alejandro Ramirez (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-323?page=history ]
Alejandro Ramirez closed BEEHIVE-323:
-------------------------------------
Verified fixed. I tested the two new methods and they are working as expected.
> It would be great to have two additional methods in PageFlowController to get and remove sharedflows.
> -----------------------------------------------------------------------------------------------------
>
> Key: BEEHIVE-323
> URL: http://issues.apache.org/jira/browse/BEEHIVE-323
> Project: Beehive
> Type: Improvement
> Components: NetUI
> Versions: V1Beta
> Reporter: Alejandro Ramirez
> Assignee: Alejandro Ramirez
> Priority: Critical
>
> Currently, we have two methods in org.apache.beehive.netui.pageflow.PageFlowUtils
> to get and remove sharedflows.
> 1.- public static SharedFlowController getSharedFlow( String sharedFlowClassName, HttpServletRequest request )
> 2.- public static void removeSharedFlow( String sharedFlowClassName, HttpServletRequest request )
> It would be great to have similar functionality under: org.apache.beehive.netui.pageflow.PageFlowController
> 1.- public static SharedFlowController getSharedFlow( String sharedFlowClassName)
> 2.- public static void removeSharedFlow( String sharedFlowClassName)
--
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-323) It would be great to have two additional methods in PageFlowController to get and remove sharedflows.
Posted by "Rich Feit (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-323?page=history ]
Rich Feit resolved BEEHIVE-323:
-------------------------------
Assign To: Alejandro Ramirez (was: Rich Feit)
Resolution: Fixed
Revision 154331. To be consistent, the argument taken is the shared flow *name* as defined in @Jpf.Controller(sharedFlowRefs=...), rather than the classname.
> It would be great to have two additional methods in PageFlowController to get and remove sharedflows.
> -----------------------------------------------------------------------------------------------------
>
> Key: BEEHIVE-323
> URL: http://issues.apache.org/jira/browse/BEEHIVE-323
> Project: Beehive
> Type: Improvement
> Components: NetUI
> Versions: V1Beta
> Reporter: Alejandro Ramirez
> Assignee: Alejandro Ramirez
> Priority: Critical
>
> Currently, we have two methods in org.apache.beehive.netui.pageflow.PageFlowUtils
> to get and remove sharedflows.
> 1.- public static SharedFlowController getSharedFlow( String sharedFlowClassName, HttpServletRequest request )
> 2.- public static void removeSharedFlow( String sharedFlowClassName, HttpServletRequest request )
> It would be great to have similar functionality under: org.apache.beehive.netui.pageflow.PageFlowController
> 1.- public static SharedFlowController getSharedFlow( String sharedFlowClassName)
> 2.- public static void removeSharedFlow( String sharedFlowClassName)
--
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