Hello, > > I am not really a Java Guru, but have made the experience > that in effect the > name "Bean" is - in the context of Struts-based Webapps - > really nothing > more than a POJO following the naming conventions of JavaBeans for > getters/setters.
Awesome, thanks! I figured as much, but I hate to assume. > With respect to the "middle layer", it really pays off to > separate "model", > "view", and "controller" and possibly separate the > persistency layer from > the model as well. > So far, I have figured that much... It might help if I explain how I am currently planning to build my application and you can all tell me whether I am way off or if it is pretty close... First, I am going to design a database, then build a bunch of beans that more or less represent the data in the database by going mostly one bean for each table. There will likely be a few cases where one bean will represent two tables (1:n relationship, where the attributes in the 'many' table come as an array of objects when the getter is called). The persistence will happen as a method of each bean. Then, I'll build forms around the navigation of the site, and have a separate layer or objects that will build and persist the beans from above. Am I on the right track? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
