I see a lot of Seam code and examples that marks methods @Transactional and immediately do em.joinTransaction before using the em. I was wondering what are the consequences of *not* following this pattern. If I were using TransactionalSeamPhaseListener, there would always be a transaction active during a request, so what's the point of using @Transactional. If I were using a seam-managed persistence context, doesn't it automatically do a em.joinTransaction()? Correct me if I'm wrong.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4045870#4045870 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4045870 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
