At the time of starting new project I used POJO beans with ease. At some point simple things ceased to work and got to work only after moving toward SFSB.
When I employed EntityHome I obtained "stale object" exception. If I understand correctly it happened because persistence context was not propagated and method parameters became detached from context. It was possible to put merge() calls left and right but code would have became too complicated. Now I normally handle UI actions by SFSBs that acts as facades and invokes several SLSB in order to access data. Normally I have several SFSB facades working with single SLSB service. In such a case tiered design helps. I came to conclusion that Seam greatly helps to start up a project with ease using such sort of components like Home, Controller and later grow up to sophisticated application with architecture you like. For me the subject of the thread is not a choise - it's evolution of your project. Seam is permanently under development and I'd like Seam experts to clarify the following questions for latest version: 1. Does JPA persistence context propagation rules work for Seam-managed conversation-scoped Beans? 2. Is there exceptional behavior in the case of EntityHome? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4123419#4123419 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4123419 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
