Well, depending on what your application does, there could be also the possibility to plan the business framework (i.e. where the logic is contained and/or the database information exchange).
The logic should contain any code not directly interacting with the web (in a work it should be portable in a non-Struts, non-web application as a package or with little modifies. To make it simple, imports to any web-related package should be avoided) and could be accomplished either by simple classes or by EJBs or by a combination of the two. The interaction with the database could be obtained either directly from the web-tier (descouraged for large-scalable applications), or from the business framework (classes or EJBs). You may want also to think at the logic inside your presentation lier (JSP? If so, how are you going to manage objects prepared by the server-side in the JSPs? JSTL and Struts-el, together with JSF are emerging technologies which you may want to consider). HTWH, Marco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
