By the way, you can always use the TransactionalSeamPhaseListener and
@TransactionAttribute(REQUIRES_NEW) to suspend the existing transaction during a
particular method call in INVOKE APPLICATION. Your method then executes in a new
transaction context - which is committed when the method returns.
As long as your are using a Seam-managed persistence context with@In EntityManager, this
should work fine even if your method calls other transactional methods that use the entity
manager. I wouldn't try this with @PersistenceContext, the rules for propagation are
complicated because they are tightly bound to the transaction propagation.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4043085#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...