That's one reason we separate the data bean from the action bean. From within the UI layer, we have the Action Bean as the controller, the Data Bean as the model, and the JSP as the view. (Of course, in a three-tier environment, the Action Bean calls the Session Bean facade to grab the back-end data to populate the Data Bean, so, from an architectural point of view, the Session Bean is the Controller, the DAOs or Entity Beans are the model, and all the JSF stuff combined is the view. I guess it depends upon one's perspective.)
- Brendan -----Original Message----- From: Slawek [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 24, 2005 3:51 PM To: MyFaces Discussion Subject: Re: confusion on best practices in regard to a VO in BackingBean now im little confused... i have started studying design patterns little before jsf and at first glance i thought that considering MVC: view is jsp page, controler is backing bean and model is pure data bean (with no business logic) now, after somme more studying i concluded that: view is jsp page AND backing bean but Rick says in his article that: view is only jsp page, controler is backing bean and model has business logic could somme guru explain relation between mvc and jsf framwework? > > Rick Hightower does this in his "Clearing the FUD about JSF" > http://www-128.ibm.com/developerworks/java/library/j-jsf1/ > > He has the XyzBeand and XyzController with the controller containing: > > XyzBean xyzBean = new XyzBean(); > > and then supporting the methods etc. via xyzBean.method() calls. His > Controller is your Action. > > See his extremely fine articles for more details. > > -david- > >
