[
https://issues.apache.org/jira/browse/FELIX-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12872130#action_12872130
]
Jean-Philippe CLEMENT commented on FELIX-2350:
----------------------------------------------
"I assume you had two issues [...]" => correct :)
I confirm that first loading the dependent library fixes the issue:
System.loadLibrary("wiiuse"); // Workaround
...
<call to something within wiiusej.jar which loads WiiuseJ.dll which loads
wiiuse.dll>
Great! Thanks a lot!!!
PS: This is a very easy and consistent workaround, so, as far as I'm concerned,
it's fine
> Bundle inner jar cannot load libraries
> --------------------------------------
>
> Key: FELIX-2350
> URL: https://issues.apache.org/jira/browse/FELIX-2350
> Project: Felix
> Issue Type: Bug
> Components: Framework
> Environment: Windows XP
> Reporter: Jean-Philippe CLEMENT
> Attachments: bluestuff-1.0.0.jar, bluestuff-1.0.1.jar
>
>
> I added a bundle which wraps a utility jar J provided by an external
> provider. This jar makes use of a dll X which uses another dll Y.
> The bundle archive contains (first level):
> com
> META-INF
> OSGI-INF
> X
> Y
> J
> The bundle manifest file contains (not complete):
> Bundle-ClassPath: .,J
> Bundle-NativeCode: X ; Y ; osname=Win32 ; processor=x86
> In order to activate the dll X, J contains a java code which does a
> System.loadLibrary("X"). This code fails when starting the bundle with the
> message (*):
> Caused by: java.lang.UnsatisfiedLinkError: no X in java.library.path
> at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1734)
> ...
> However, moving the System.loadLibrary to the direct bundle java code
> succeeds. Then everything is fine.
> Looks like it is a bug.
> (*) Failing code appears in the java class loading part, i.e. static {
> System.loadLibrary(...) }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
