Comments on: Speak like a native – How to use native code (Windows DLL) in OSGi

By: Lars Vogel

Lars Vogel — Fri, 30 Jul 2010 07:28:02 +0000

@masaya in this case the jco3.jar expects the .dll on the same level. This is not a limitation of OSGi.

By: masaya

masaya — Fri, 30 Jul 2010 01:21:30 +0000

Does the Dlls have to be in the *main path* of our bundle ?
I tried to put it in sub folder. such as /native/sapjco3.dll.
But It failed…

By: Heath Borders

Heath Borders — Thu, 29 Jul 2010 05:16:29 +0000

@Alex

Do you know why the unload limitation exists? I know you can load/unload .so’s on linux, I assume mac and windows allow it as well.

By: Lars Vogel

Lars Vogel — Tue, 27 Jul 2010 12:02:02 +0000

@Alex thanks for the clarification.

By: Alex Blewitt

Alex Blewitt — Tue, 27 Jul 2010 11:50:30 +0000

Note that the DLL is loaded once: so if you do this, you should really make the bundle a singleton as well. If you uninstall and reinstall the bundle it may not be possible to install and reload it in the same process.

Also, the DLL interdependencies can be a problem. It’s best to have a shim which provides a (constant) Java API, then code tour vundles against that API in a different bundle.