You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2012/08/21 14:59:38 UTC
[jira] [Commented] (SLING-2570) Use Wiring API to check whether
Installer Core bundle is affect by a bundle update
[ https://issues.apache.org/jira/browse/SLING-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438686#comment-13438686 ]
Bertrand Delacretaz commented on SLING-2570:
--------------------------------------------
Note that in testing SLING-2567 I noticed that the installer.core bundle was affected by updating a bundle to which the installer is wired by a DynamicImport-Package clause - I don't know enough about the wiring API so far to know if that will help in that case.
This will probably go away with SLING-2568, as it's the javax.servlet package which is dynamically imported and that will go away - but I'm still wondering if this method of detecting that the installer will be stopped when certain bundles are refreshed is reliable - also considering that in my case this happens at startup in a system upgrade, while many bundles are being started/updated/replaced.
> Use Wiring API to check whether Installer Core bundle is affect by a bundle update
> ----------------------------------------------------------------------------------
>
> Key: SLING-2570
> URL: https://issues.apache.org/jira/browse/SLING-2570
> Project: Sling
> Issue Type: Improvement
> Components: Installer
> Affects Versions: Installer Core 3.3.8
> Reporter: Felix Meschberger
>
> Recently support has been built into the OSGi installer to check whether update of bundles affects the Installer bundle itself (for wiring reasons). This is currently implemented using the deprecated PackageAdmin service.
> For newer platforms where the OSGi Wiring API is available, the newer API should be used for that check. This makes our code simpler and cleaner.
--
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