Thanks Gavin for the reply.
I finally figured something out. Working with new technology is always fun,
even if it is a bit frustrating. I'm very new to using EJB3 - in fact I
switched to using it (from tomcat/hibernate) when seam was still in it's first
releases (mainly cvs at that time)
Why not just use @PersistenceContext?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4059280#4059280
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4059280
___
jboss-user mailing
Thanks - I'll give that a try. I didn't try since once I figured out how to use
@In
EntityManager em
I didn't look at this piece again and I forgot about it. Now that I've been
through a more in depth learning process, I won't forget about this again
(actually I probably never really learned
1. You can use standard EJB3 mechanisms for transaction demarcation, which
certainly lets you have multiple transactions.
2. An asynchronous method gets a a new temporary conversation context. It
cannot access the conversation context from which it was spawned.
HTH
View the original post :
