[ 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
