|DLL hell with different bundles in Eclipse Equinox [message #558476]
||Mon, 13 September 2010 08:04
| Bjoern Berg
Registered: November 2009
I have a question about sharing a needed DLL for a JDBC2-driver between two different bundles that need access to the driver.
The scenario: In my RCP application I integrated the BIRT Runtime environment to execute pre-defined reports in the application. That works perfect, when the appropriate drivers for the database (Oracle driver) are stored to " org.eclipse.birt.report.data.oda.jdbc_2.5.2.v20100205\driver s ". Then I have another bundle that needs access to the database and the same Oracle driver. The problem is, the DLL needed by the JDBC driver is loaded by another Classloader and I get an Unsatisfied Link Exception which is correct so far.
I tried to load the DLL by the VMs Classloader adding it at startup time with -Djava.library.path, but that does not work.
So, what is the best practice to share a driver between different bundles? How did you do that?
Powered by FUDForum
. Page generated in 0.03144 seconds