This thread is for discussing JBAS-7507 and its implementation.
When nested transactions support is explicitly disabled (the default), we need to throwing
a NotSupportedException if a remote (or even local) client calls UserTransaction.begin()
twice on the same thread with no rollback/commit in between.
A larger question is whether or not we should be supporting nested transactions at all.
While Arjuna supports them, it seems that there is little practical application for them
based on comments from Mark Little and others since not many resource managers support
them. If we don't throw a NotSupportedException when the Arjuna nested transactions
flag is enabled, then we have to ensure that code like the tx sticky load balancing
policies support them (more work, and I imagine there are many other examples too).
Dimitris asked that we discuss the implementation for the throwing of the NSE in the
disabled case, and that's the focus of JBAS-7507, but I think there is potentially a
larger question here too (that may be a different discussion, however).
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4270092#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...