Seam allows you structure your application in any number of ways. There is nothing preventing you from calling your business tier objects from your Seam components (e.g. inject your business tier services through @EJB). Then your Seam components call the business tier objects to perform the business logic and persistence. Think of Seam not as UI and persistence framework, but as an application framework that sits on top of your business tier. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086751#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...