Thanks for your response, It's very helpful.

I would like to disable it becuase the lazy enlistment feature inconsistent 
with spring transaction for inner transactional.

Scenario
1. Begin outer transaction by spring aop.
2. Get connection, the connection is enlisted to outer transaction.
3. Begin inner transaction by spring aop.
4. CCM try to enlist the same connection to the inner transaction again. It 
throw an exception "Trying to change transaction [...] in enlist.

If I purely use JBoss transaction, can you explain me how the JBoss notify CCM 
when it has an inner transactional. Does it push a new MetaAwareObject to local 
stack or do something else? I will report an issue to Spring.

Thanks

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203519#4203519

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203519
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user

Reply via email to