You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (JIRA)" <ji...@apache.org> on 2018/06/15 08:08:00 UTC
[jira] [Updated] (SLING-7736) OSGi Installer: Update OSGi
installer's resource state in case of manual configuration/bundle updates
[ https://issues.apache.org/jira/browse/SLING-7736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Windszus updated SLING-7736:
-----------------------------------
Description:
Currently the state of an OSGi installer's resource is only updated whenever it is newly added to the queue and subsequently processed. Manual configuration/bundle changes outside of the OSGi installer don't change the OSGi installer's resource state.
Actually, with the help of the {{BundleListener}} (https://osgi.org/javadoc/r5/core/org/osgi/framework/BundleListener.html) and the {{ConfigurationListener}} (https://osgi.org/javadoc/r5/cmpn/org/osgi/service/cm/ConfigurationListener.html) the OSGi installer could mark the according OSGi installer resources as {{IGNORED}} in case they have been overwritten.
The tricky part is to filter out those event's which have been caused by the OSGi installer itself.
That would improve the effectiveness of the health check from SLING-5888 and also allows the OSGi installer to better enforce its state during reinstallation in the future.
was:
Currently the state of an OSGi installer's resource is only updated whenever it is newly added to the queue and subsequently processed. Manual configuration/bundle changes outside of the OSGi installer don't change the OSGi installer's resource state.
Actually, with the help of the {{BundleListener}} (https://osgi.org/javadoc/r5/core/org/osgi/framework/BundleListener.html) and the {{ConfigurationListener}} (https://osgi.org/javadoc/r5/cmpn/org/osgi/service/cm/ConfigurationListener.html) the OSGi installer could mark the according OSGi installer resources as {{IGNORED}} in case they have been overwritten.
That would improve the effectiveness of the health check from SLING-5888 and also allows the OSGi installer to better enforce its state during reinstallation in the future.
> OSGi Installer: Update OSGi installer's resource state in case of manual configuration/bundle updates
> -----------------------------------------------------------------------------------------------------
>
> Key: SLING-7736
> URL: https://issues.apache.org/jira/browse/SLING-7736
> Project: Sling
> Issue Type: Bug
> Components: Installer
> Affects Versions: Installer Core 3.8.10, Installer Configuration Factory 1.2.0
> Reporter: Konrad Windszus
> Priority: Major
>
> Currently the state of an OSGi installer's resource is only updated whenever it is newly added to the queue and subsequently processed. Manual configuration/bundle changes outside of the OSGi installer don't change the OSGi installer's resource state.
> Actually, with the help of the {{BundleListener}} (https://osgi.org/javadoc/r5/core/org/osgi/framework/BundleListener.html) and the {{ConfigurationListener}} (https://osgi.org/javadoc/r5/cmpn/org/osgi/service/cm/ConfigurationListener.html) the OSGi installer could mark the according OSGi installer resources as {{IGNORED}} in case they have been overwritten.
> The tricky part is to filter out those event's which have been caused by the OSGi installer itself.
> That would improve the effectiveness of the health check from SLING-5888 and also allows the OSGi installer to better enforce its state during reinstallation in the future.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)