Hi all,

I readed some similar thing about JSF/model/database issues.

I have a simple and effective "model/architecture"  for JSF practice.  We have developed 4 projects in JSF/OJB.  They are all password protected, so I can't demo to you. The first 2 projects we bumped lots hard things. JSF still is baby, we needs lots of  takecare things. I feel and belive, if JSF want to continue and make as common tools, we need add lots of functional components, not just tag components. This may take a few years.
Back to  the topic, the key thing is  if you want use JSF, you have to keep database operation far from JSF beans. (I call those beans as  FORM BEAN) .  My model is simple, straight, effective and works, here is  basic tiers logic :

JSF pages --  {FORM  BEAN}* --  {VALUE OBJECT(Abstract)} - {DAO/OJB} - DATABASE

I have a Core packages. for Each of OJB Object, it automatically copy value between Value Object and OJB object, using java reffect when it needs. all actions/handlers proccess data to FORM BEANs. In form bean you have method for saveings, deleting, updating and etc, depends on your business logic, you can refresh data from database or just save data in session or request scope.
 
Remember, the key thing is never have getters/setters tie to DAO/OJB. It will cause lots of trouble, including headache one - if dataModel==0 then get it.

Zhong Li

WebJabber.Net

Reply via email to