Tim Holloway wrote:NO version of Java should have been able to locate a JDBC driver just because you drop it into a JDK or JRE directory...
Well, no. The OP apparently dropped the driver into the
extensions directory in the past, a feature with its pros and cons. Personally I got burned by it a couple of times -- for example if you move your application to a different system or upgrade to a new JRE (as in this
thread) you have to make sure you copy your "extension" over into the new system's extensions directory. Which you will probably forget to do because you forgot you dropped it there in the first place.
It's true that the later versions of the JRE don't have an "ext" directory under the "lib" directory. Whether you could just create your own and carry on, or whether the extensions directory has been discontinued, I don't know. But I would recommend just putting the JDBC driver in the classpath -- everybody should know how to set up their classpath anyway.