|summary:||Fix for issue https://glassfish.dev.java.net/issues/show_bug.cgi?id=8520 (propagate SQLException to the client): - In XA ('jts') the code rolls back transaction only for the RuntimeException in bC callbacks, which allows to j|
|date:||2009-08-20 23:19:46 UTC (5 years)|
|message:||Fix for issue https://glassfish.dev.java.net/issues/show_bug.cgi?id=8520 (propagate SQLException to the client):
- In XA ('jts') the code rolls back transaction only for the RuntimeException in bC callbacks, which allows to j
ust rethrow it.
- J2EETransaction is changed for the local calls to add the caught exception to the RollbackException. Because t
he signature cannot be changed, added call to initCause().
- JDOException had been written before JDK 1.4 (or because we supported 1.3 at that time) so it had it's own su
pport for the nested exception. Instead of changing the api, made the nested exception available from both metho
ds, the JDOException.getNestedException() and Throwable.getCause().
ejb devtests and modified ejbflush test passed.