Knut Anders Hatlen wrote:

>I'm not sure what's the best way to handle InstantiationException and
>IllegalAccessException. Maybe we could print a message to the console
>saying "Unexpected error when loading Derby JDBC 4.0 driver. Please
>check that your derbyclient.jar is not corrupted. Will fall back to
>JDBC 3.0."
>
>  
>
There is no console as such for the client and normally running inside
an app so we don't want anything going to System.out, so I don't think
that is an option.  I haven't looked closely enough at the issue to say
what is an option, however.


Reply via email to