Loading the JDBC driver jar dynamically from external location
There is a possible performance issue in connecting and disconnecting from a database with each request.  Setting up a connection can be expensive, so if these connections are not pooled/cached/reused on the driver level, you may want to look into libraries or techniques for JDBC connection pooling.

(Also be sure to close connections you get from your driver.  Database connections are external resources that can not be reliably handled by the garbage collectors, and need to be explicitly cleaned up.)

As far as I can tell, you already have the driver you want; why work through DriverManager?  Ask your driver for the connection:


  Connection   connect(String url, Properties info)
  
  Attempts to make a database connection to the given URL.


The reflection workaround assumes that the system class loader is an URLClassLoader and that you have the privileges to call its addURL method.  That's not necessarily true, especially for a server environment.

And, uh, I don't think it really needs saying, but the error handling is... less than optimal. ;-)