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]
