When you use convention you don't have to use annotation: /person -> com.myapp.actions.Person#execute (SUCCESS) -> person.jsp /person-edit -> com.myapp.action.Person#edit -> person-edit.jsp /person-submit -> com.myapp.actions.Person#submit -> person-submit.jsp || person-input.jsp
2014-05-26 11:41 GMT+02:00 Antonio Sánchez <[email protected]>: > I'm trying to define a generic/abstract action and extend or instantiate it > with specific actions. > > Say a generic/abstract CRUDaction and have UserAction, InvoiceAction etc... > to instantiate/extend it. > > I don't see the way to do this using Conventions. I believe it is possible > using wildcards. Using conventions I am forced to override abstract methods > using Action annotations. But probably I am wrong so, please, let me know if > I can use Conventions bearing in mind this design approach. > > > > El vie 23 may 2014 11:06:10 CEST, Lukasz Lenart escribió: >> >> Why don't use the Convention Plugin? >> >> 2014-05-23 10:58 GMT+02:00 Antonio Sánchez <[email protected]>: >>> >>> Hello. >>> >>> Given: >>> >>> <action name="*Person" class="some.package.PersonAction" >>> method="{1}"> >>> <result >>> name="input">/WEB-INF/jsp/editPerson.jsp</result> >>> <result >>> name="success">/WEB-INF/jsp/persons.jsp</result> >>> </action> >>> >>> And url: >>> >>> http://localhost:8080/appctx/Person >>> >>> No matching is found and Struts redirects to "input" result directly. In >>> order to recognize "Person" as an action additional configuration is >>> required: >>> >>> <action name="Person" class="..." method="list"> >>> <result >>> name="success">/WEB-INF/jsp/persons.jsp</result> >>> </action> >>> >>> Is there anyway of avoiding this extra definition, just using the >>> wildcard >>> one? >>> >>> >>> >>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
