1) How many classes? It depends on what your webapp does. You're the Only one who can answer that.
2) Which and how many POJOS? See number one above. 3) I find it easiest to start with a prototype of the web application and go backwards from there. Note data-driven fields. Note all forms. Note all data-driven links. Is there any special processing required to render pages? This will let you to surmise the POJOs and actions required. From there you can model your DB according to the POJOs. Depending on what your web app is supposed to do, it may be very easy to define the DB tables based on the POJOs, and the table columns based on The POJO attributes. This is most advantageous for CRUD-type of apps. Your situation may be different. -----Original Message----- From: Casinova [mailto:[EMAIL PROTECTED] Sent: Friday, October 24, 2008 10:39 AM To: user@struts.apache.org Subject: Struts Project Planning Hi all, I am creating struts web application. i need suggestion from u all. how can i planning my application . my application using database . 1) how to decide how many classes and which are those required? 2) what about POJOs ? how many and which are they required? 3) should i create classes according to tables in DB? and more suggestion if u have any.. Thanks in advance, -- View this message in context: http://www.nabble.com/Struts-Project-Planning-tp20151405p20151405.html Sent from the Struts - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Notice: This e-mail message, together with any attachments, contains information of Merck & Co., Inc. (One Merck Drive, Whitehouse Station, New Jersey, USA 08889), and/or its affiliates (which may be known outside the United States as Merck Frosst, Merck Sharp & Dohme or MSD and in Japan, as Banyu - direct contact information for affiliates is available at http://www.merck.com/contact/contacts.html) that may be confidential, proprietary copyrighted and/or legally privileged. It is intended solely for the use of the individual or entity named on this message. If you are not the intended recipient, and have received this message in error, please notify us immediately by reply e-mail and then delete it from your system. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
