You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2012/08/14 19:06:37 UTC
[jira] [Resolved] (SLING-2556) Installer should detect if installer
bundle is refreshed by another bundle update
[ https://issues.apache.org/jira/browse/SLING-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler resolved SLING-2556.
-------------------------------------
Resolution: Fixed
> Installer should detect if installer bundle is refreshed by another bundle update
> ---------------------------------------------------------------------------------
>
> Key: SLING-2556
> URL: https://issues.apache.org/jira/browse/SLING-2556
> Project: Sling
> Issue Type: Improvement
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Installer Core 3.3.8
>
>
> If e.g. the logging bundle is updated through the OSGi installer, this causes the logging bundle to be refreshed which in turn causes the OSGi installer to be restarted.
> However as the OSGi installer is not aware of this fact, it is waiting for a package refresh event, and is holding references in an async thread. This is turn sometimes causes the bundle stop/start of the installer bundle to fail.
> Therefore the OSGi installer should detect this situation and stop itself - the same as it already does for updating itself.
> With the R4.3 wiring api, this is easily to detect; without it, it gets harder - we should have an implementation which detects whether R4.3 is available and uses this functionality. If its not available it should use a fallback
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira