Commit adea17e
committed
Bypass DriverManager for JDBC connections loaded at runtime
When the Oracle JDBC jar is added to the load path at runtime (rather
than being on the system classpath), java.sql.DriverManager refuses
to hand out connections with "No suitable driver". Fall back to
calling ORACLE_DRIVER.connect directly with username/password
properties so the connection still succeeds.
The fallback is scoped narrowly: only Java::JavaSql::SQLException
whose message matches /no suitable driver/i triggers it; any other
SQLException (auth/network/SQL errors) re-raises so the original
error surfaces unchanged.
Apply the same change in spec/spec_helper.rb so the JRuby test
harness behaves consistently.1 parent dbf19f3 commit adea17e
2 files changed
Lines changed: 27 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
35 | 35 | | |
36 | 36 | | |
37 | 37 | | |
38 | | - | |
| 38 | + | |
| 39 | + | |
39 | 40 | | |
40 | 41 | | |
41 | 42 | | |
| |||
51 | 52 | | |
52 | 53 | | |
53 | 54 | | |
54 | | - | |
| 55 | + | |
| 56 | + | |
| 57 | + | |
| 58 | + | |
| 59 | + | |
| 60 | + | |
| 61 | + | |
| 62 | + | |
| 63 | + | |
| 64 | + | |
| 65 | + | |
| 66 | + | |
| 67 | + | |
55 | 68 | | |
56 | 69 | | |
57 | 70 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
88 | 88 | | |
89 | 89 | | |
90 | 90 | | |
91 | | - | |
| 91 | + | |
| 92 | + | |
| 93 | + | |
| 94 | + | |
| 95 | + | |
| 96 | + | |
| 97 | + | |
| 98 | + | |
| 99 | + | |
| 100 | + | |
| 101 | + | |
| 102 | + | |
92 | 103 | | |
93 | 104 | | |
94 | 105 | | |
| |||
0 commit comments