Hi Achim, thanks for pointing out the issue with dynamic linked libraries, indeed I did not pay attention to the magic word "dynamic" in the blog post. My problem is currently that I'm not really into this topic, but have to deal with it from the Java side. Therefore, two questions:
1. We have only a single native library, so no reference problems between dynamic libs, like you've mentioned. In fact, we actually don't use .dll, but .so on linux arm, but that should be the same for loading in OSGi. > Therefore create a statically linked A.dll How can this be done? I thought a .dll is always dynamic linked? 2. > the name might need to be "Dynamic" as the container might rename the dll > because a dll can't be unloaded unless the corresponding class-loader is > destroyed. During this time the second native library will be renamed. Like said, there is no second native library which could be renamed. What do you mean by the "Dynamic" name? Best regards Patrick -- View this message in context: http://karaf.922171.n3.nabble.com/Native-library-and-System-load-tp4032562p4038253.html Sent from the Karaf - User mailing list archive at Nabble.com.
