sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konrad Windszus (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SLING-7736) OSGi Installer: Update OSGi installer's resource state in case of manual configuration/bundle updates
Date Fri, 15 Jun 2018 08:13:00 GMT

     [ 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 (but most probably the checksum from the installer's state can be used, to detect if
the actual content has been changed)

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.

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.


> 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 (but most probably the checksum from the installer's state can be used, to detect if
the actual content has been changed)
> 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)

Mime
View raw message