Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Message-ID: <9648759.931274888258032.JavaMail.jira@thor>
Date: Wed, 26 May 2010 11:37:38 -0400 (EDT)
From: "Richard S. Hall (JIRA)" <jira@apache.org>
To: dev@felix.apache.org
Subject: [jira] Commented: (FELIX-2350) Bundle inner jar cannot load
 libraries
In-Reply-To: <8508575.40821274361665316.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/FELIX-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12871775#action_12871775 ] 

Richard S. Hall commented on FELIX-2350:
----------------------------------------

What am I missing? If this is related to native library loading, then it is a framework issue, not a Karaf issue.

> 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
>    Affects Versions: karaf-1.4.0
>         Environment: Windows XP
>            Reporter: Jean-Philippe CLEMENT
>
> 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.