Order in which SynchronousBundleListeners are called

Hi there, I made a SynchronousBundleListener listening for bundle 0 to detect when the container shuts down, because I want to do some cleanup stuff before. In theory this works. Problem is: There are lots of other bundles that use the same "technique" (like Camel, Blueprint, etc.). And their Sy

Re: Order in which SynchronousBundleListeners are called

Hello Neil, On Fri, Sep 20, 2013 at 11:52 AM, Neil Bartlett wrote: > On Fri, Sep 20, 2013 at 10:42 AM, Frizz > wrote: > > It seems the only way to "control" the order in which > > SynchronousBundleListenes are called is via the bundle start level (e.g. > &g

JNI: unloading a DLL from the container

, because I'm still in the development phase of the DLL - so the code changes quite frequently. So I need a way to REDEPLOY my bundle (I usually do a dev:watch during development). Any suggestions? cheers, Frizz

Re: unloading a DLL from the container

ean-philippe.clem...@fr.thalesgroup.com> wrote: > Hi, > > 1. As far as I know you cannot > 2. Maybe GlueGen can help you (NativeLibrary) > > JP > > -Message d'origine- > De : Frizz [mailto:frizzthe...@googlemail.com] > Envoyé : mardi 18 mars 2014 06:35 &

Classloader exception

#x27;t the bundles classloader be gone once I uninstalled the bundle? cheers, Frizz

Re: Classloader exception

n and its abilities to load native code? > I haven't found anything useful yet - can you point me in the right direction? cheers, Frizz

Set System Property With Blueprint Configuration File

I am trying to set a System Property in my Blueprint Configuration File, similar to the Spring approach that is described here: http://stackoverflow.com/questions/3339736/set-system-property-with-spring-configuration-file My code looks like this: org.blabla.package