Hi, I'm in the process of trying out hot deploy in using servicemix. As per the documentation, all I need to do is to drop the bundle in the deploy folder and servicmix will take care of deploying it. Here's what I did followed by my questions.
I've a bundle foo-1.0.0.jar which exports bar-1.0.0.jar. Now, I added some changes in bar-1.0.0.jar and changed the version to bar-1.1.0.jar. I then copied the file to the deploy forlder and waited for a min (default polling rate is 1 sec). When I ran the test case, it showed results from bar-1.0.0 instead of the new version. The servicemix log also pointed to the fact that it was referring to bar-1.0.0. Now,I changed the version back to bar-1.0.0, build the jar and copied it to deploy folder. I ran the test case and was able to see the changes. So, it works fine if I've the same version. What I'm trying to understand is how to hot deploy a new version of a running bundle. Is it supported by the hot deploy feature ? The doubt I've is explained through the example below : In foo-1.0.0 pom file, I've imported bar-1.0.0 as <Import-Package>com.bar;version=1.0.0</Import-Package>, which gets reflected in the manifest as part of the import-package as well export-package. Now,if I'm able to hot deploy bar-1.1.0 , how'll bundle foo's manifest going to be updated ? Do I need to provide a version range in foo's pom so that any update in bar is covered ? <Import-Package>com.bar;version=1.0.0, 2.0.0</Import-Package>. I'll appreciate if someone can clarify my doubts in this regard. - Thanks
