We have been using Turbine for some time but we have this philosophical question:
When a should a java functionality should be implemented as an action or in the .java file of a screen? Some cases are clearly actions like adding a record to the database. Other cases are clearly screens like displaying an items information. Other cases are not as clear like searching for records in the database or doing a validation on a form. The rule of thumb we have been using is: If it modifies the database is an action. Screens should never modify the database. (or for that matter the state of the application) We looked in the information on the turbine site and didn`t find a reference on the subject. A related question would be what is the matching between MVC and Turbine: Controller = TurbineServlet + Actions. View = Screens + Layouts + Navigations. Model = Entity Beans + Session Beans = Peers Object Model + (?) What would correspond to session beans in the model. Actions? Screens? Additional Java Objects? If you do a setTemplate() within a Screen.java, Shouldn`t that be parte of the controller? We are kind of confused and would like to understand this better to make a good use of Turbine. -- Humberto -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
