[FRG-122] FarragoJdbcClientDriver should use FarragoJdbcUtil.newSqlException() to wrap non-SQLExceptions

[dynamobi-build]

[reporter="hersker", created="Tue, 2 May 2006 17:13:40 -0500 (GMT-05:00)"] Exception handling cleanup to parallel that done in DT codebase.

Currently, FarragoJdbcClientDriver throws new SQLException(e.getMessage()) where it should more safely use FarragoJdbcUtil.newSqlException(ex, tracer). However, the Farrago client driver does not have a tracer.

Two obvious choices:

• add tracer to FarragoJdbcClientDriver
  
• add newSqlException(ex) method (without tracer) to FarragoJdbcUtil
  
  The DT client driver has its own tracer, so it seems that the FarragoJdbcClientDriver should, too. But the DT client driver gets its tracer from AspenClientTrace for use in the JDK 1.4-compatible client driver Jar. There is no FarragoClientTrace module at this time, so a new one would be needed.
  
  This expands the scope of a solution past a one-liner quick fix. As I am currently unfamiliar with the usage of the Farrago client driver, I need more information before deciding the best implementation approach. This Jira ticket is a placeholder to remind us to revisit this at a more appropriate time.

[dynamobi-build]

[author="hersker", created="Tue, 2 May 2006 18:12:53 -0500 (GMT-05:00)"] Searching for "new SQLException" in Farrago reveals many other classes that need the same fix.