[ http://issues.apache.org/jira/browse/BEEHIVE-165?page=comments#action_57630 ] John Rohrlich commented on BEEHIVE-165: ---------------------------------------
I've reproduced the bug. I don't see a problem limiting shared flows to directories that don't contain global.app but we do need to warn because the reason for the invalid action error is not obvious. > Actions in SharedFlows located next to global.app do not seem to work > --------------------------------------------------------------------- > > Key: BEEHIVE-165 > URL: http://issues.apache.org/jira/browse/BEEHIVE-165 > Project: Beehive > Type: Bug > Components: NetUI > Versions: TBD > Environment: windows xp, tomcat 5.0.25, (beehive synched to svn 125107) > Reporter: Alejandro Ramirez > Assignee: Rich Feit > Attachments: SharedFlowSources.zip > > 1.- Unzip the attached set of PageFlows into a webapp. Notice that there is > a "GlobalSharedFlow.jpfs" shared flow that should go under WEB-INF/src/global. > 2.- Deploy the webapp with the new set of pageflows > 3.- Navigate to: > http://localhost:<yourPort>/<yourWebapp>/SharedFlowTest/SharedFlowController.jpf. > From there, click the link "Go to Action Tests". > Expected: That link should take you to: > /SharedFlowTest/SharedFlow1/index.jsp. In that page, there is an anchor tag > that reference the action "globalSharedFlowAction" which is in the shared > flow "WEB-INF/src/global/GlobalSharedFlow.jpfs". The expected result is that > the anchor tag should work. > Actual: The anchor tag throws an error: > Message: Action 'globalSharedFlow.globalSharedFlowAction' 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
