One thing to be careful of, a mistake I've seen made often, is a clean separation of the business delegates and the Actions... When calling on your delegates, be sure NOT to pass anything that is web-specific like session or request objects. This will make changing business classes a lot easier and will also allow you target other types of clients without changing your business code. To most it seems an obvious point, but I've seen the rule broken many times, and 99% of the time it wasn't necassery.
-- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com On Tue, September 21, 2004 6:01 am, [EMAIL PROTECTED] said: > A common practice is to use the J2EE design pattern "Business Delegate", > that provides a clean separation between the technology used to store data > and all the rest of the application. > The Business Delegate will expose some "APIs", but it does not show how it > is really implemented (JDBC, EJB,etc.) > For more information take a look at: > http://java.sun.com/blueprints/patterns/BusinessDelegate.html > Ciao > Antonio Petrelli > > >> In the mailing list, I have read some people suggesting not to put >> business logics in Action class. Certainly, business logics should not >> be in JSP or Form class. Then where should the business logics be put? >> >> Thanks >> >> > > > --------------------------------------------------------------------- > 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]
