-
1. Re: Seam vs EJB3 container managed persistence contexts
christian.bauer Feb 24, 2007 1:06 PM (in response to flashguru)Search for my posts on this forum, I've explained the differences at least once at length.
-
2. Re: Seam vs EJB3 container managed persistence contexts
gavin.king Feb 24, 2007 1:59 PM (in response to flashguru) -
3. Re: Seam vs EJB3 container managed persistence contexts
flashguru Feb 24, 2007 2:30 PM (in response to flashguru)Sorry, my question was a bit vague and misleading.
What I really wanted to confirm is that if I use @PersistentContext then Seam will not intercept this and return a Seam managed persistent context (SMPC).
I was led to think that way because I saw a seam interceptor (org.jboss.seam.ejb.SeamInterceptor) being added as an EJB3 interceptor.
But, now that I have looked at the code for SessionBeanInterceptor, the purpose of this interceptor is to detect the creation of the session bean and treat it as a seam component if the session bean has the @name annotation. -
4. Some seam examples are using EJB managed PC
flashguru Feb 24, 2007 4:16 PM (in response to flashguru)The booking example RegisterAction is using EJB3 managed PC instead of Seam managed PC.
Is this intentional? Or is it because in this specific scenario, it does not matter which one you use?
Thanks again. -
5. Re: Seam vs EJB3 container managed persistence contexts
gavin.king Feb 24, 2007 4:32 PM (in response to flashguru)It doesnt matter in the booking demo, because there is just one component involved in the conversation. If there were lots of components collaborating, you would probably be better of with a Seam-managed PC.