[
https://issues.apache.org/activemq/browse/SMX4KNL-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43169#action_43169
]
Guillaume Nodet commented on SMX4KNL-44:
----------------------------------------
Digging into this issue a bit more, i think the refreshPackages(bundleChanged)
has to be called, and called after starting / updating the other bundles.
Unfortunately, when doing so, we hit a problem with Spring-DM: Spring-DM 1.0.x
uses Dynamic-Import, and refreshing a spring app leads to spring-extender being
refreshed, therefore all the spring DM applications are refreshed too. It
seems this problem will be solved when switching to Spring DM 1.1 + Spring
2.5.4.
However, I'm not sure that it will fix the original bug, which is that the
updated bundle is restarted twice (further investigation is needed).
> Changed bundles restarted twice
> -------------------------------
>
> Key: SMX4KNL-44
> URL: https://issues.apache.org/activemq/browse/SMX4KNL-44
> Project: ServiceMix Kernel
> Issue Type: Bug
> Affects Versions: 1.0-m3
> Reporter: Ivan Stojic
> Fix For: 1.0-rc1
>
>
> When a bundle file is replaced or 'touch'-ed in the deploy directory, the
> bundle is being restarted twice.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
