Thanks for your answers, I have another questions:

1.- When I developed applications with JSF I used a JSF/Spring/Hibernate 
architecure using Managed Beans/Services/DAOs, the managed beans had the 
presentation logic, the Services had the business logic and the DAOs had the 
data access logic, it was there were I performed my hibernate queries. 

On the examples I've seen the entity beans would be the object that I 
manipulated on with the DAOs, but I have also seen that the session bean 
contains data, business and presentation logic. The jsp is being managed from 
there, business rules are being applied on its methods and it is also making 
queries to the database. I suppose this is just for the simplicity of the 
event, but how can I separate efficiently this three layers? What's the closest 
thing you can do to the Service/DAO pattern on JBoss Seam?

2.- When database queries were done on the example I didn't see any transaction 
being open, does JBoss Seam manage them transparently like Spring or were they 
omitted on the example?

Thanks again

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069428#4069428

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069428
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user

Reply via email to