The Rod Johnson book entitled "J2EE development without EJB" suggests NOT using DAO pattern when the business tier components are doing mostly persistence code. In that case, it's not worth abstracting the data access tier. In Pro Spring book, the writer(s) do not recommend a 1-to-1 ratio of DAO to tables in RDBMS. How would you implement caching using DAO pattern w/ SEAM? In SEAM apps, it seams to me the SFSB's are doing mostly persistence api work. So perhaps that's why the examples in the SEAM distribution do not use DAO? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4076349#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...