Unless you have a very simple system, if you have networks of interconnected persistent objects that have to stay in sync, you pretty well have to use some sort of transaction management to cover all the myriad ways you could fail.
Without some sort of transaction manager, it requires expontially complicated code to back out of every possible failure. The code cannot be fully exercised during debugging and it will only fail at the JavaOne demo before the people from HP (Hewlett Packard) who are thinking of bundling your product with every computer they sell.
The three most common ways of doing transaction management are SQL, EJBand PODs.
|
|
You can get the freshest copy of this page from: | or possibly from your local J: drive (Java virtual drive/mindprod.com website mirror) |
| http://mindprod.com/jgloss/transaction.html | J:\mindprod\jgloss\transaction.html | |
![]() | Please email your feedback for publication,
letters to the editor, errors, omissions, typos, formatting errors, ambiguities, unclear wording,
broken/redirected link reports, suggestions to improve this page or comments to
Roedy Green :
| |
| Canadian Mind Products | ||
| mindprod.com IP:[65.110.21.43] | ||
| view Blog | Your face IP:[38.107.179.210] | |
| Feedback | You are visitor number 10,905. | |