Daniel Rall wrote:
> >
> > Maybe you could use TurbineException (or a custm derivate of it) ?
>
> That would've been great. However, the PooledConnection interface
> needs to throw a SQLException. SQLException and TurbineException are
> both solid classes, so there is no way to extend both. I think we
> need to do something like you suggest, however. Perhaps we need an
> interface similar to what TurbineException presents. This isn't the
> only place where we rethrow exceptions--and lose the stack trace in the
> process--because we need to throw a specific type of exception.
Ah I undestand. It's not easy to get around this one. I guess that
Logging
the stacktrace at the point and throwing the specific Exception class is
indeed the way to go here.
Rafal
--
Rafal Krzewski
Senior Internet Developer
mailto:[EMAIL PROTECTED]
+48 22 8534830 http://e-point.pl
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
