anonymous wrote : Seam still uses a 3-layered architecture. Ok, it breaks with traditional J2EE patterns like DAOs and stuff. But hey, this is called "progress". You do not need this fat old architecture paradigmas. But you can still use them if you want to. If it is necessary you can still have a session bean as a wrapper around the EntityManager. I sometimes use this pattern, if the retrieving of entities is more complex and does happen - at least sometimes - outside of seam. This is useful if you have MDBs and you don't want them to depend on seam so you can deploy them on another AppServer more easily. Regards fhh View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971513#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...