hi rafael,
i guess you are deploying your application in an ee-server.
in such a case you have to be aware of [1] (see the usage with
@PersistenceUnit EntityManagerFactory).
the rest (= wrapping the EntityManager) is the same.
regards,
gerhard
[1] http://deltaspike.apache.org/jpa.html
Do you know if the functionality of the link above only works with the
Conversation scope?
2014-04-09 0:09 GMT-03:00 Gerhard Petracek gerhard.petra...@gmail.com:
hi rafael,
please provide a demo-application which illustrates the issue.
back then it worked and since your own disposer calls
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?
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 rafaelmeire...@gmail.com wrote:
Hello everyone, I would like to
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 karl.kil...@gmail.com:
I am also curious about best practice for this (right now) and perhaps in
the
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
hi rafael,
please provide a demo-application which illustrates the issue.
back then it worked and since your own disposer calls #close, it should
still work.
regards,
gerhard
2014-04-09 2:04 GMT+02:00 Rafael Meireles rafaelmeire...@gmail.com:
I looked this link when I started my project,
