I think the way to solve the problem would be to modify servicemix
so that when a shared library is upgraded, the components that depend
on it are shut down, the library upgraded, and the components started
again.
It should be the standard behavior and I think this is an oversight.
Please raise a JIRA and provide a patch if possible.
There are three possible models here:
1) Keep what you get at runtime
2) Force all to new version at once
3) Managed versioning
Each has significant implications for mangement of deployed products in
a live environment.
I think ideally you should be able to choose the strategy you want to
use to fit with your environment.
--
Terry
