Description Caspar D. 2010-06-16 03:16:18 EDT

In 3.0 the CommitException was introduced. It serves roughly
the same purpose (as far as my understanding goes) as
TransactionException, the only difference being that the new
type is a checked exception while the old is unchecked.

But we haven't properly eliminated the
TransactionExceptions. They still get thrown from many
places, and then get wrapped in a CommitException. But
TransactionException itself is also a wrapper, so that now
the real "cause" exception is typically at least 2 layers
deep. We should eliminate this unnecessary wrapping.

(Another odd thing is that CommitExceptions themselves
get wrapped in TransactionExceptions first if new code
throws one from somewhere within the commit logic. And that
TxException then gets wrapped into another "outer"
CommitException again.)