btw to expand on your first question. Just because there is little code needed, doesn't mean there aren't design patterns or maybe the better term is "good design". Since Seam comes pre-loaded with soo many options you are going to have lots of decisions to make. ie: - When to use a Stateful vs Stateless vs JavaBean - When to use the query objects as a DAO layer vs when to call it on your own from the business teir with the entity manager. - Scopes, when to apply each scope, determining when it's appropriate - Heck even down to when the EB / SB NEEDS to be a Seam component vs just being a regular EB / SB / Pojo. But as Pete said ... it's mostly up to you. Just be careful i've noticed beginners tend to take some easy ways out. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4124934#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...