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?
Maurice.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@felix.apache.org
For additional commands, e-mail: users-h...@felix.apache.org
