Try J2EE design patterns (http://java.sun.com/blueprints/corej2eepatterns/Patterns/index.html).
Suzette H. Daniel -----Original Message----- From: Adam Hardy [mailto:[EMAIL PROTECTED] Sent: Thursday, July 24, 2003 7:12 AM To: Struts Users Mailing List Subject: model - controller interface I'm just about to write all the factory classes in tomcat (to connect via JDBC to the DB) for the updates and other CRUD my app will do. I am going to write methods for my actions to call, with a parameter for each item of data on the objects to be updated, e.g.: treeHuggerFactory.update(id, name, treeId, huggyId, expireDate, isHopeless); Then it occurred to me there might be a more intelligent OO design approach, especially since I want to change from using JDBC to EJB at some point. Should I be wrapping the object up in a bean and just passing the bean around, instead of listing all the properties? I'm thinking of the ease of maintenance in the future when things change as well. Anybody got any advice? Thanks Adam --------------------------------------------------------------------- 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]
