[ https://issues.apache.org/struts/browse/STR-2309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Benedict closed STR-2309. ------------------------------ Resolution: Won't Fix > Wildcard support in global forward declarations (and possibly other places) > --------------------------------------------------------------------------- > > Key: STR-2309 > URL: https://issues.apache.org/struts/browse/STR-2309 > Project: Struts 1 > Issue Type: Improvement > Components: Core > Affects Versions: 1.2.4 > Environment: Operating System: All > Platform: All > Reporter: Anton Maslovsky > Assignee: Don Brown > Priority: Minor > > It would be great to have wildcard support not only in action definitions, > but > also in some other struts-config elements, such as global forwards, ex: > <forward name="/admin/*User" path="/admin.do?method={1}User"/> > This should allow to use forward definitions like "editUser", "deleteUser", > etc. > This also might be usefull for form bean definitions. Consider the follwing > example: > <action path="/user*" type="com.company.{1}User" name="{1}UserForm" input="{1} > User.jsp"/> > I may have, say 5 actions, most would be using form beans with the same > properties ôòâ different name, but one of them uses a different form bean: > <form name="*UserForm"> > <form-property name="name" type="String"> > </form> > <form name="changePasswordUserForm"> > <form-property name="name" type="String"> > <form-property name="oldPassword" type="String"> > <form-property name="newPassword" type="String"> > </form> > Ãûøòï wildcards would allow to avoid defining several form beans with the > same > set of properties but just different names. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.