A struts 1.x solution would be to include generic edit* mappingThis example employs wildcard characters for Naming Action Classes,specifying Form Name,Forwarded pathhttp://struts.apache.org/1.2.9/userGuide/building_controller.html<!-- Generic edit* mapping implemented with <action path="/SomeName*" --><!-- Note the use of parameters for consructing name of Action Classes e.g. EditAAction,EditBAction --><!-- Note the ability to select a specific Form based on the parameter passed in AForm, BForm --><!-- Note the capability of forwarding to specific jsp based on parameter passed in as in A.jsp,B.jsp--> <action path="/edit*" type="org.apache.struts.webapp.example.Edit{1}Action" name="{1}Form" scope="request" validate="false"> <forward name="failure" path="/mainMenu.jsp"/> <forward name="success" path="/{1}.jsp"/> </action>Anyone else?Martin --This e-mail communication and any attachments may contain confidential and privileged information for the use of the designated recipients named above. If you are not the intended recipient, you are hereby notified that you have received this communication in error and that any review, disclosure, dissemination, distribution or copying of it or its contents ----- Original Message ----- From: "David Pinho (Hexadecimal)" <[EMAIL PROTECTED]> To: "Struts Users Mailing List" <user@struts.apache.org> Sent: Wednesday, November 29, 2006 5:55 AM Subject: RE: Design
Have you looked into Struts Menu? It has a declarative approach where you can specify menus in xml but also a taglib that may allow you to build them dynamically. It's pretty nifty. Regarding the navigation, I'd stick with the first solution you pointed out. Using inheritance seems a bit overkill plus it reduces the decoupling between your actions (suppose you want to use them outside of the menu context). David -----Original Message----- From: Michel Van Asten [mailto:[EMAIL PROTECTED] Sent: quarta-feira, 29 de Novembro de 2006 9:53 To: Struts Users Mailing List Subject: Design Hi, We have to developp a new application and we want to with a good design. Basically we have a set of functionalities (user management, user data control, user data conversion, ...) the availabilty of those functionalities is controlled via a dynamic menu. Hi planned to define one action for each functionality. But for the menu whats the best solution ? I see two solutions : 1° Adding an extra action for the menu and implement Action chaining if I need to jump back to the menu. 2° All the actions extends a base class wich implement menu management routine and I use global forward. Regards, Michel Van Asten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] AVISO Esta mensagem e quaisquer anexos seus podem conter informação confidencial para uso exclusivo do destinatário. Cabe ao destinatário assegurar a verificação de vírus e outras medidas que assegurem que esta mensagem não afecta os seus sistemas. Se não for o destinatário, não deverá usar, distribuir ou copiar este e-mail, devendo proceder à sua eliminação e informar o emissor. É estritamente proibido o uso, a distribuição, a cópia ou qualquer forma de disseminação não autorizada deste e-mail e seus anexos. Obrigado. DISCLAIMER This e-mail and its attachments may contain confidential information for exclusive use of its recipient. It is your responsibility to carry out appropriate virus and other checks to ensure that this message and any attachments do not affect your systems / data. If you are not the intended recipient you must not use, distribute or reproduce this e-mail and you must notify the sender and delete the entire email. Any unauthorized use, dissemination, distribution or copying of this message and its attachments is strictly prohibited. Thank You. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
