http://www.javaworld.com/javaworld/jw-01-2009/jw-01-spring-transactions.html
http://www.javaworld.com/javaworld/jw-04-2007/jw-04-xa.html
Bozho
2010-04-27 15:48:10
views:
59answers:
2
+2
A:
Questions to ask yourself/team:
- Does our database support XA?
- Does the JDBC driver support XA?
- Will the combination of Glassfish/database/JDBC work with XA?
- Do we really need distributed transactions?
I'll return to point 4 - don't do distributed transactions. You need to be really sure that distributed transactions are the best solution for you. It isn't simple and the recommendation is to avoid them, if possible. This comes straight from Jürgen Höller, co-founder and senior developer at Spring.
Spring has no support for propagating transactions between processes, so you'll need the container to support this or manually do this yourself.
hbunny
2010-04-27 16:08:47
Well, I am not sure I need distributed transactions, but how can I provide a solution, where you could call E1 (which internally calls Base) and Base, for eg. on a WebService, and maintain atomicity?
pihentagy
2010-04-28 09:04:18
One approach (and I don't know if this fits your problem domain or not) is to use asynchronous message passing - the definitive work on this is http://www.enterpriseintegrationpatterns.com/
hbunny
2010-04-28 09:51:48
Have not looked into it, but will it allow me to cooperate applications to decide an outcome (commit/rollback) of a complex (multi-application) action? It seems to be a solution for a system with loosely coupled applications.
pihentagy
2010-04-28 15:30:47
Will not use distributed transactions. Everything will go to one war file.
pihentagy
2010-04-30 15:33:38