And if you really like DispatchAction go a step further an try LookupDispatchAction.
Shed. -----Original Message----- From: McDonnell, Colm (MLIM) [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 30, 2004 3:41 To: Struts Users Mailing List Subject: RE: Searching pattern/best-practise for forms > I've tried some ways to do this and ended up with three actions for one > form: one for setting it up, one for displaying and validating it and > one for the selected backend action. I just wonder if that is a good way > or if I'm introducing some problems into my applications. The Struts DispatchAction is a neat way of combining multiple operations on a single entity into one Action class. See http://husted.com/struts/tips/002.html for more details on this approach. -----Original Message----- From: Alexander Czernay [mailto:[EMAIL PROTECTED] Sent: 30 November 2004 08:31 To: Struts Users Mailing List Subject: Re: Searching pattern/best-practise for forms Hollaway, Shedrick L CIV TRIREFFAC wrote: > Alexander, > This should help you understand applying DAO/DTO patterns in a Struts > app: http://javaboutique.internet.com/tutorials/ApacheDAOs/ > > Shed. > Thanks for all your replys and suggestions, but I'm afraid I didn't ask the right question. What I really wanted to know was, how you would organize the controller/view in Struts for handling those standard create/update/delete actions. Like you have a database containing an address-book in the backend and want to display it as a list to the user, so he can select entries for editing/deletion or create new ones. When creating/editing entries you would present those as a form, validate it and write it back to the backend. I've tried some ways to do this and ended up with three actions for one form: one for setting it up, one for displaying and validating it and one for the selected backend action. I just wonder if that is a good way or if I'm introducing some problems into my applications. Alexander --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -------------------------------------------------------- If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
smime.p7s
Description: S/MIME cryptographic signature
