-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Class loader doesn't seem to load JDBC drivers #44
Comments
Having looked at it several evening this week, I haven't been able to solve it. |
I tested and work fine, I can't reproduce the issue with a postgresql driver, e.g.: [https://gist.github.com/rodrigoSaladoAnaya/11063062] The problem must be that the jar is not in the classpath, or that the jar you use has a problem. If I have a mistake and instead of
Regards. |
Hi @jpokrzyk, you can add this snippet and verify that the driver is included? //Show classpath elements
System.getProperty('java.class.path').split(':').each {
println "> ${it}"
} Regards. |
K. I can't remember exactly how I was doing this originally. vertx runmod works fine if I put the jdbc.jar in the lib folder. Don't know if I previously tried that. I might have been trying to us grape. I still can't get it to work with gradle. Here's the code: https://dl.dropboxusercontent.com/u/416599/gist.zip Here's the classpath dump with vertx runmod
Here's the classpath from gradle runmod
But feel free to close this if you don't want to work on it. If I'm using gradle, it's a larger-ish project and I would be using mod-jdbc anyways. With 'vertx run' I was probably trying to do this with grape. And after thinking that one through definitely understand why vertx wouldn't pick up what grape downloads. Thanks for te follow up though. |
Groovy class loader won't load JDBC drivers. See https://groups.google.com/forum/#!topic/vertx/djXxGfOClt0.
Here's some sample code to reproduce error:
https://gist.github.com/jpokrzyk/8109151
Seems like this one is beyond my skill level to fix but if you don't get to it in a few days I'll take a look.
The text was updated successfully, but these errors were encountered: