Andy, thank you for this help so far. Unfortunately the transaction-managament is not an unimportant issue in my application I would like to let EJB3 do the work.
This is what I found in another thread. This is, what Bill Burke recommends in such a situation. anonymous wrote : deploy your entities as you would but assign them a JNDI name(see docs). In your EJB interceptor pick the appropriate JNDI name of the EntityManager you want to access. Either inject the ENtityManager into the field of your bean using a custom annotation, or stuff the chosen entity manager into a java.lang.ThreadLocal. This way you still get the automatic session management that the EJB/Java Persistence integration gives you. Following me? Did you try this way as well? I don´t see if this could be a real solution to this problem. Thank you Thomas View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3951869#3951869 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3951869 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
