Feb 27th, 2011, 02:56 PM
Strange Behavior in SpringDM when refreshing Dependencies
I have a Bundle A which defines a simple JAXRS resource and the exports that package. I have another Bundle S which defines a spring context in which the bean from A is instantiated. To do this, of course, S imports the package from A. Now, I modify the bean in A and then 'osgi update' bundle A. Then I 'osgi refresh'
A I would expect that to automatically refresh S and then re-wire S so that it connects to the new version of the package exported by A and thus S should see a new version of the bean.
Funny thing is, this works about 5% of the time. The other 95% of the time the bean defined in A simply vanishes from S. It's like S is looking for the old version of the packages and when it can't find them it simply silently gives up.