Re: [DISCUSS] Persistent wiring framework

I came up with the following extension: https://github.com/apache/karaf/blob/master/features/extension/src/main/java/org/apache/karaf/features/extension/Activator.java It seems to work correctly so far. I suppose it would be even faster to have it in the framework to avoid going through the

Re: [DISCUSS] Persistent wiring framework

2016-10-03 22:12 GMT+02:00 Karl Pauls : > On Mon, Oct 3, 2016 at 9:49 PM, Guillaume Nodet wrote: > > > An extension sounds doable. > > However, I found something weird: > > > > https://github.com/apache/felix/blob/trunk/framework/ > >

Re: [DISCUSS] Persistent wiring framework

On Mon, Oct 3, 2016 at 9:49 PM, Guillaume Nodet wrote: > An extension sounds doable. > However, I found something weird: > > https://github.com/apache/felix/blob/trunk/framework/ > src/main/java/org/apache/felix/framework/ExtensionManager.java#L505-L507 > > Is that expected

Re: [DISCUSS] Persistent wiring framework

An extension sounds doable. However, I found something weird: https://github.com/apache/felix/blob/trunk/framework/src/main/java/org/apache/felix/framework/ExtensionManager.java#L505-L507 Is that expected that the framework is using the classloader loading the framework instead of the

Re: [DISCUSS] Persistent wiring framework

On 10/3/16 12:02 , Guillaume Nodet wrote: I have a use case where the wiring is a bit complicated. Karaf uses the felix resolver to compute the full wiring and then applies it. At this point, all the bundles are resolved and started correctly. If Karaf is restarted, the framework restarts and

[DISCUSS] Persistent wiring framework

I have a use case where the wiring is a bit complicated. Karaf uses the felix resolver to compute the full wiring and then applies it. At this point, all the bundles are resolved and started correctly. If Karaf is restarted, the framework restarts and resolves the bundles on its own, using a bad