I have a rather large problem with my guice entitymanager. I followed the guide supplied on the guicePersist pages but I still seem to be having issues. I don't use the open session in view filter (and I'm not planning to use this) The problem is guice is reusing my session context in my threads. So when I call a method, annotated with the @Transactional attribute, my entity manager is reused when I start hitting the same threads on my webserver (rest endpoints). Because I don't want to use Provider<EntityManager>.get each time, I have wrapped this in a proxy with delegate methods. These delegate methods call provider.get.method(). This proxy is a eagerSingleton, injected over my whole application. This mean the provider each time should start a new entityManager when in the same jpalocaltxninterceptor. I can't believe I'm the only person who is trying this, so I suppose I must be doing something wrong, but I cant figure out what exactly. I have created a stackoverflow thread, but then I didn't really know what the exact problem was http://stackoverflow.com/questions/23503484/jpa2-reuses-entitymanager-with-guice
-- You received this message because you are subscribed to the Google Groups "google-guice" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-guice. For more options, visit https://groups.google.com/d/optout.
