– https://docs.google.com/viewer?a=v&q=cache:pbI9dp4CB4wJ:java9s.com/wp-content/uploads/2012/06/Spring-Transactions.ppt+bmt+cmt+in+spring&hl=en&gl=us&pid=bl&srcid=ADGEESiWHmG93nXhIa12PdJor-s7HmVfCTEV8BKIW6mvWljy2kH-dxYock_0lKckhUg1TL2UKTkVKKTVx0aGu-BLrNjzOxBJC1505ToRB0T-5xqYBmmzoog63lEayd9Fvb9bAbggpObZ&sig=AHIEtbTq4Db4BtA4Bc2Tn4ADfBr-vfpFuw (Srinivas Reddy http://www.java9s.com)
– CMT needs an application server and tied to JTA, but spring doesn’t
– spring _Declarative_ tx = CMT w/o application server
– Programmatic transaction management is usually a good idea only if you have a small number of transactional operations and need fine control over them.
– spring tx limitation: only for a single db, no build-in JTA support
– Spring tx managers delegate the responsibility to platform specific transaction
– Spring tx managers act as facade to platform specific transaction impl
– platform specific tx mgrs: datasourcetxmgr, hibernatetxmgr, jpatxmgr, jtatxmgr