Hi Amit, I took the same approach - different pages for different functionalities. However, all pages use the same action to add/edit/delete the data since the code was so simliar.
It's worked out pretty well so far. Obviously, the only pain is when I think of a better way to do something and then I have to go through all the pages to change it. But I'm pretty happy with it now so I don't need to do this very often. You can also look at the sample application at http://zebra.tigris.org to see how they did it. Good luck, David -----Original Message----- From: Amit V Shah [mailto:[EMAIL PROTECTED] Sent: Thursday September 2, 2004 9:27 AM To: '[EMAIL PROTECTED]' Subject: Duplicating Pages Hi all, I have an application where I need web pages for like add, edit, delete some data, which more or less represent the same data, and only have small differences in terms of their requirements. In such case, is it better to have a same JSP, or a Velocity Template and flag it based on the option user selects, or is it a better idea to have different pages for each option?? I dont know if this is the right forum to ask this question so please pardon me and disregard if this question doesnot belong in here. I just want to have like an architectural opinion as to what would be the best practise and what could be the considerations that I should be going through. I prefer to having different pages for different functionalities rather than flagging the pages, and actions and all that stuff because in my opinion flagging only complicates things and leads to bugs which could be very complicated to figure out, and then even worst to fix ... Thanks, Amit --------------------------------------------------------------------- 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]
