RE: Uninstalled API bundle, yet implementation still resolves and starts

It should be noted that the OSGi specification clearly states that the framework must not try to replace the old API bundle classes in such cases where those classes are still being used until a refresh is requested, as others pointed out. So this is not a work-around but rather how the system

Re: Uninstalled API bundle, yet implementation still resolves and starts

I 'solved' it by restarting the device. I rather don't, as I like solution where I can upgrade functionality without shutting down. Basically my structure is as follows: Bundle A: API Bundle S: Service (uses and provides some API implementation from A) Bundle X1..N: Provide functionality for S

Re: Uninstalled API bundle, yet implementation still resolves and starts

Sorry Hadn't realised it was a running framework! On Wed, Nov 4, 2015 at 11:11 AM, Neil Bartlett wrote: > > > On 4 Nov 2015, at 11:07, Robert Onslow wrote: > > > > Delete the directory called felix-cache?? > > No, in his second email he says that

Re: Better go go shell

Understood. Thanks. On 11/4/15, 12:19 PM, "Guillaume Nodet" wrote: >My goal was not to provide a jline based console on top of the existing >runtime, I've already done that in Karaf years ago, the goal was to >integrate the jline3 code base and provide new features, hence

Re: Uninstalled API bundle, yet implementation still resolves and starts

On 11/4/15 06:52 , i...@cuhka.com wrote: I 'solved' it by restarting the device. I rather don't, as I like solution where I can upgrade functionality without shutting down. You don't need to shut down, you just need to refresh the framework. If you update A and S, the old version of A is

Re: Better go go shell

Dear Guillaume, Ah, I see. You are using gogo runtime version 17.0 as a dependency. This forces everyone to update gogo runtime, and backward compatibility suffers greatly, and I am unsure of the maturity of V0.17 Do you think the use of version 16.0 or lower makes sense, as the console would

Uninstalled API bundle, yet implementation still resolves and starts

I have an API bundle and and implementation bundle. I removed both the API and implementation, re-installed the implementation and started the implementation. To my suprise the framework was willing to start the bundle, even though the API isn't there anymore. It was present, so obviously

Re: Uninstalled API bundle, yet implementation still resolves and starts

Maybe I should also not that there are still started bundles that use the old API, I haven't updated them yet. But I thought that are all different classloaders, isolating from each other. Citeren i...@cuhka.com: Is this assumption incorrect?

Re: Uninstalled API bundle, yet implementation still resolves and starts

> On 4 Nov 2015, at 10:37, i...@cuhka.com wrote: > > I have an API bundle and and implementation bundle. I removed both the API > and implementation, re-installed the implementation and started the > implementation. To my suprise the framework was willing to start the bundle, > even though

Re: Uninstalled API bundle, yet implementation still resolves and starts

Delete the directory called felix-cache?? On Wed, Nov 4, 2015 at 10:42 AM, Neil Bartlett wrote: > > > On 4 Nov 2015, at 10:37, i...@cuhka.com wrote: > > > > I have an API bundle and and implementation bundle. I removed both the > API and implementation, re-installed the

Re: Uninstalled API bundle, yet implementation still resolves and starts

> On 4 Nov 2015, at 11:07, Robert Onslow wrote: > > Delete the directory called felix-cache?? No, in his second email he says that other bundles are still running that use the old API. So we’re talking about a series of changes made in a running OSGi Framework, and