Most of the write-ups about Seam emphasize how much it helps integrate the user interface (JSF) with the persistence layer. But what about a layered architecture where we don't want them together? I'm working on a project where JSF will be used to rewrite and extend the user interface of an existing application. In many cases, business logic is already embedded in a business layer that will be reused. We intend to maintain this separation of concerns, keeping business logic away from the UI. The UI will never talk to the persistence layer, only the the business layer. How does Seam fit into this kind of a model? Given that we want to use dependency injection in the business layer, does it make sense to use Seam or is something like Spring sufficient? Thank you in advance for any advice. Rob View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086704#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...