[
https://issues.apache.org/activemq/browse/SMX4KNL-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved SMX4KNL-44.
------------------------------------
Assignee: Guillaume Nodet
Fix Version/s: 1.0-rc2
(was: 1.0-rc1)
Resolution: Fixed
I think the only way to fix the original problem is to have an explicit call to
refreshPackages through a command, but I doubt it is a good solution, as imho,
users expect the updated bundle to be used immediately.
So with the fix at revision 662445, when a bundle in the deploy dir is
'touch'ed, the following happens:
* the bundle is updated, which means it is stopped, updated, resolved and
start again
* if the bundle is in use (some packages are imported by other bundles), a
graph of dependent bundles is computed by the framework and they are all
stopped / resolved / started again
This means that for a "library" which only contains code, the bundle will be
restarted twice, once for the update and another one with all the dependant
bundles. For an "application" where packages are not imported by other
bundles, the bundle will be restarted only once.
I've tried to make that better, but the refreshPackages is handled
asynchronously by the framework, which means there is no simple way to stop
bundle, call refreshPackages() and restart the bundle later.
http://svn.apache.org/viewvc?rev=662445&view=rev
> 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
> Assignee: Guillaume Nodet
> Fix For: 1.0-rc2
>
>
> 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.
