[ http://issues.apache.org/jira/browse/BEEHIVE-1038?page=all ] Julie Zhuo closed BEEHIVE-1038: -------------------------------
Verified with rev372375. The roles are now merged correctly. > rolesAllowed specified in the inheriting pageflow class does not get merged > --------------------------------------------------------------------------- > > Key: BEEHIVE-1038 > URL: http://issues.apache.org/jira/browse/BEEHIVE-1038 > Project: Beehive > Type: Bug > Components: NetUI > Versions: 1.0.1 > Environment: Windows and Tomcat > Reporter: Julie Zhuo > Assignee: Julie Zhuo > Fix For: 1.0.1 > Attachments: InheritancePageflow.zip > > This is a regression. I have this working before. > In the parent pageflow controller class the attribute specified as follow, > @Jpf.Controller(loginRequired = true, > longLived = true, > rolesAllowed = {"role1", "role2"}, > readOnly = true, > multipartHandler = Jpf.MultipartHandler.memory, > strutsMerge = > "/testInheritance/parent/controllerAttr/struts4merge.xml") > In the extending page flow controller class, the attribute is specified as > the following, > @Jpf.Controller(rolesAllowed = {"role3", "role4"}) > public class ControllerAttrController extends > testInheritance.parent.controllerAttr.ControllerAttrController > { > } > Expecting all 4 roles showing up in the struts config file. The query only > showing role1 and role2 from the parent class since the generated struts > config file does the following, > <action > className="org.apache.beehive.netui.pageflow.config.DelegatingActionMapping" > parameter="testInheritance.merge.controllerAttr.ControllerAttrController" > path="/loginAction" scope="request" validate="false"> > <!-- Note that there is more than one action with path "/loginAction". > Use a form-qualified action path if this is not the one you want. --> > <set-property property="overloaded" value="true"/> > <set-property property="delegateModulePath" > value="/testInheritance/parent/controllerAttr"/> > </action> > Will attach a repro page flow shortly. -- 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
