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.
- Re: [jira] Updated: (DERBY-796) jdbc 4.0 specific B... Kathey Marsden
- Re: [jira] Updated: (DERBY-796) jdbc 4.0 speci... David W. Van Couvering
- Re: [jira] Updated: (DERBY-796) jdbc 4.0 s... Daniel John Debrunner
- Re: [jira] Updated: (DERBY-796) jdbc 4.0 s... Kathey Marsden
- Re: [jira] Updated: (DERBY-796) jdbc 4... Satheesh Bandaram
- Re: [jira] Updated: (DERBY-796) jd... David W. Van Couvering
- [jira] Updated: (DERBY-796) jdbc 4.0 specific ... V.Narayanan (JIRA)
- [jira] Updated: (DERBY-796) jdbc 4.0 specific ... V.Narayanan (JIRA)
- [jira] Updated: (DERBY-796) jdbc 4.0 specific ... V.Narayanan (JIRA)
- [jira] Updated: (DERBY-796) jdbc 4.0 specific ... V.Narayanan (JIRA)
