As we've discussed over the past few issues, JTA-style transactions provide a
way for multiple data updates to be tied together so application logic can
operate safely in the assumption that it will succeed or fail consistently,
even in the face of technical failures along the road.
There are, however, times when you do not want all the work you do to succeed
or fail in one big lump.
Among the scenarios that may lead you to want to break work up into smaller
chunks are: Progress/error logging Long-running operations Wide-spanning
operations I discussed the last two scenarios in a... (more)
This month's article is again inspired by an interesting design discussion
posted on the weblogic.developer.transaction newsgroup. (Ever get the feeling
I'm running short of inspiration? Ideas for new articles always welcome!)
Since the problem described is a common one with transactional design I
thought it might be valuable to review the design, the problems with it, and
some solutions.... (more)
As we've discussed over the past few issues, JTA-style transactions provide a
way for multiple data updates to be tied together so application logic can
operate safely in the assumption that it will succeed or fail consistently,
even in the face of technical failures along the road.
I have often mused, in this column and outside, on how bizarre it seems that
I have filled over two years w... (more)
Sad, I mused - you don't often see that any more. My mind then wandered to
hoping that, as technologists, we aren't somehow tacitly colluding in the
erosion of the fabric that holds society together. Hmm, I seem to have come
over all melancholy. Excuse me whilst I visit The Hunger Site...
Understanding JTA
That's better. Anyhow, I digress. I promised to look this month at when to
use tran... (more)