Would you mind elaborating a bit on what you mean by this? On Tue, Oct 6, 2015 at 9:21 AM, CLEMENT Jean-Philippe < [email protected]> wrote:
> Just a thought, why not wrapping the native libraries and expose them as a > regular OSGi service through an API? > > > > JP > > > > [@@ OPEN @@] > > > > *De :* craig niles [mailto:[email protected]] > *Envoyé :* lundi 5 octobre 2015 20:39 > *À :* [email protected] > *Objet :* Karaf instances and native libs > > > > Hi, > > I have an important piece of middle-ware that depends on native > libraries. I have a requirement to support multiple implementation of this > middle-ware simultaneously. To accomplish this I want to start child karaf > instances from my main process. > > I'm using an extender pattern to detect when a bundle is installed that > provides the middle-ware. When detected, it extracts the required native > libs from the bundle to the instance lib directory (e.g. > $KARAF_HOME/instances/foo-01/lib). > > I've found an issue, however, with the way LD_LIBRARY_PATH is being set > when the instance is started using the instance's start script--the > KARAF_BASE variable isn't set to the instance's directory and > consequentially LD_LIBRARY_PATH doesn't include the instance's lib > directory when ran. This isn't a problem, however, when started with the > instance's karaf script. > > Does anyone have any ideas or guidance on how to handle this? >
