This ticket: https://issues.apache.org/jira/browse/TINKERPOP-1004
discusses the idea of generalizing transaction exceptions. We already have a general AbstractTransaction.TransactionException class, but it gets swallowed by a RuntimeException in the default implementation of the AbstractTransaction. I think we can just solve TINKERPOP-1004 by just having TransactionException extend RuntimeException and making TransactionException a class of its own. I tend to think that is a good-enough solution as: 1. it doesn't place any new burden on providers, is lightweight and is already largely in place 2. i'm reasonably sure that many graph providers already use AbstractTransaction and didn't bother to write their own so they get this change for free basically 3. user code has the minor change of not having to unwrap the TransactionException anymore I'd like to do this for 3.3.0. I'll assume lazy consensus after 72 hours if there are no objections. Thanks.
