However, it simply calls Transaction.rollback(con) which can throws NullPointerException if con is null. This breaks alot of my code since I use safeRollback extensively for precautionary measure. Furthermore, the signature for rollback declare that TorqueException will be thrown and does not specify NullPointerException.
I think this issue has been partly dealt with by a recent commit by John McNally just a couple of days ago. I say partially because the implementation was not ideal and needs to be updated as per Henning's reply to this list. The suggested behaviour is for rollback(con) to simply return when con is null.
Scott --
Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
