[jboss-user] [JBoss Seam] - How best to leverage Seam when you've got a HUGE domain?

Hi folks, It looks like we will end up using a very large domain model, IBM's Insurance Application Architecture: http://www-03.ibm.com/industries/financialservices/doc/content/solution/2... In a perfect world, we will not expose this complexity to the folks working on the UI. We thought about how to do this. One thought was to provide sort of a component as facade, inject the entitymanager into that component, and make it responsible for doing the persistence itself rather than delegating it to another component (action) like we see in most of the examples. Another thought was to implement the "service" model where all of the persistence work is delegated to DAOs or services. This *seems* conceptually easier for the majority of folks to understand, but I'm not sure. At the very least this is how folks seemed to use Struts type systems. Sort of backwards, but I think we can still leverage the power of Seam minus one big sweet spot. What are your thoughts on this? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057703#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...