> On 4 Nov 2015, at 10:37, [email protected] 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 the API isn't there anymore. It was present, so obviously it is > using some cached class. > > I encountered this because I changed the signature of the API, updated all > bundle versions and redeployed it. The implementation resolved fine, but > didn't run because it could not find the updated signature. > > Personally I would have expected the implementation bundle to have picked up > the changed api, and after uninstalling to not resolve. Is this assumption > incorrect?
No, this is basically correct. However your description of the scenario is too vague to be able to tell exactly what happened in this case. If you specify which bundles import and export which packages, and what you did to those bundles in sequence, then we might get somewhere. Neil > > Maurice. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
