I looked this link when I started my project, but this solution doesn't work. This solution just create a entity manager with the conversational scope and the entity manager stay serialized, but with this solution, the entity manager doesn't stay open during the conversation.
About the best practice of the extended persistence context, here we have a project in production with seam 2, JSF 1.2, EJB 3 and JPA 1, running in a JBoss Application Server and this system is used by many people in the state of Ceará, Brazil. We have around 300 - 400 users concurrent and the Application Servers are in Cluster. Can you explain better, this: "the Deltaspike /CDI style is very nice to work" 2014-04-08 9:01 GMT-03:00 Gerhard Petracek <[email protected]>: > hi, > > please have a look at [1]. > > regards, > gerhard > > [1] > > https://cwiki.apache.org/confluence/display/EXTCDI/JPA+Usage#JPAUsage-ExtendedPersistenceContexts > > > > 2014-04-08 13:37 GMT+02:00 Karl Kildén <[email protected]>: > > > I am also curious about best practice for this (right now) and perhaps in > > the future. The thing is the Deltaspike /CDI style is very nice to work > > with and it would be a preferred API for me. > > > > > > On 8 April 2014 13:33, Rafael Meireles <[email protected]> wrote: > > > > > Hello everyone, I would like to know if you think about create an > option > > > that exists in seam 2, that I can open the entitymanager for many > > requests? > > > > > > -- Atenciosamente, -------------------------------------------- Rafael Meireles Caetano Arquiteto Java EE Sefaz - CE Fone: +55 85 8811-1806
