[EMAIL PROTECTED] wrote:
>
> I agree with Frank and John. I also agree with John that this is a pain in
> the ass to go back and implement since it will change so much code. So, my
> vote is that Kevin has the itch, so he should scratch it. ;-) Personally,
> I don't feel that it is that hard to read the output of printStackTrace()
> to find the location of the problem.
That isn't really the issue. The issue is something like
try {
//do something with Turbine
//do something with JDBC
//call your own API that uses both Turbine and JDBC
} catch (TurbineException e) {
//handle turbine problems
} catch (SQLException e) {
//handle SQLExceptions
}
...
Kevin
--
Kevin A Burton ([EMAIL PROTECTED])
http://relativity.yi.org
Message to SUN: "Open Source Java!"
"For evil to win is for good men to do nothing."
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
