The error message would seem to indicate differently. Right now the driver appears to just say that it's not valid at all for the connection
String, so DriverManager skips it completely. If I'd have written that driver I would have chosen a different error message and throw an SQLException from the driver itself.