1. You can implement any architectural pattern you like with Seam, it does
not impose an architecture. Of course, some things that were needed in J2EE or
in JSF/Spring/Hibernate are simply not necessary in Seam.
2. Check the documentation about Seam-managed transactions.
View the original post
magoicochea wrote : 1.- How is persistence managed? Does it use EJB 3.0
persistence (I don't know much about EJB) or can I use hibernate? If it uses
Hibernate how is it implemented? As usual with Hibernate or does it uses some
kind of annotations for it?
Seam provides a Seam Managed
To answer your questions:
1. Seam works with either EJB3 or Hibernate. I'm using EJB3 in my projects
because EJB3 is a standard. I think that Hibernate itself is a bit more
powerful in what it can do. Under the hood, JBoss EJB3 is based on Hibernate I
believe.
2. Don't use Tomahawk. I
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,
