This is an automated email from the ASF dual-hosted git repository.
kwin pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/sling-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new e2bbdc4 OSGi Installer HC clarifications
e2bbdc4 is described below
commit e2bbdc45292a8b20779ac24ee39eb02fa4a14c8f
Author: Konrad Windszus <[email protected]>
AuthorDate: Fri Jun 29 15:17:32 2018 +0200
OSGi Installer HC clarifications
---
documentation/bundles/osgi-installer.html | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/documentation/bundles/osgi-installer.html
b/documentation/bundles/osgi-installer.html
index 5ffc2f7..8b94ab4 100644
--- a/documentation/bundles/osgi-installer.html
+++ b/documentation/bundles/osgi-installer.html
@@ -137,12 +137,15 @@
<h2><a href="#health-check" name="health-check">Health Check</a></h2>
<p>The OSGi installer provides a <a
href="/documentation/bundles/sling-health-check-tool.html">Sling Health
Check</a> which validates that the processed OSGi installer resources have the
correct state (<a
href="https://issues.apache.org/jira/browse/SLING-5888";>SLING-5888</a>). By
default it will only check resources with a URL prefix
<code>jcrinstall:/apps/</code>, so only the resources being provided through
the <a href="/documentation/bundles/jcr-installer-provider.html">JCR Installer
[...]
<h3><a href="#bundles-installation-failure"
name="bundles-installation-failure">Bundles Installation Failure</a></h3>
-<p>The checked bundle was not installed because it has been installed in a
newer version through some other means (e.g. manually through the Felix Web
Console or by another provider. For further details please review the OSGi
Installer console at <code>/system/console/osgi-installer</code> and check for
all bundles with the given symbolic name (=OSGi installers resource id) and the
according URL.</p>
+<p>The checked bundle was not installed because it has been installed in a
newer version from some other location (might even be through some other
provider). For further details please look at the OSGi Installer console at
<code>/system/console/osgi-installer</code> and check for all bundles with the
given symbolic name (=OSGi installer's resource id) and their according
URLs.</p>
<h3><a href="#configuration-installation-failure"
name="configuration-installation-failure">Configuration Installation
Failure</a></h3>
-<p>The checked configuration was not installed because it has either been
overwritten manually in the Felix Web Console or is installed by some
non-checked provider (which has a higher priority). To revert manually
overwritten configurations just go to <code>/system/console/configMgr</code>
and delete the according configuration. That way the OSGi installer should
automatically create a new configuration for the same PID based on the
configuration provided by some provider with the highe [...]
+<p>The checked configuration was not installed because it is already installed
from some other location (which has a higher priority). In this case you can
see from where it has been installed by looking at the OSGi Installer console
at <code>/system/console/osgi-installer</code> and check all configurations
with the given PID and their according URLs.</p>
+<p>Due to <a
href="https://issues.apache.org/jira/browse/SLING-7735";>SLING-7735</a>, there
might be false positives being reported by the health check, in case the
configuration has already been deployed with exactly the same values in the
system previously. In that case the OSGi Installer might also mark the resource
as <code>IGNORED</code>. If you run into such an issue, you can fix it by
removing the manually overwritten configurations: Just go to
<code>/system/console/configMgr</code [...]
+<h3><a href="#limitations-of-the-health-check"
name="limitations-of-the-health-check">Limitations of the health check</a></h3>
+<p>Currently the health check and the OSGi installer cannot detect if a
deployed bundle/configuration has been overwritten (e.g. via API or the
WebConsole). So even if an OSGi installer resource is marked as
<code>INSTALLED</code> it might already have been overwritten. This limitation
is tracked in <a
href="https://issues.apache.org/jira/browse/SLING-7736";>SLING-7736</a>.</p></section></div></div>
<div class="footer">
<div class="revisionInfo">
- Last modified by <span class="author">Robert
Munteanu</span> on <span class="comment">Wed Nov 22 22:30:38 2017 +0200</span>
+ Last modified by <span class="author">Konrad
Windszus</span> on <span class="comment">Fri Jun 29 15:15:19 2018 +0200</span>
</div> <p>
Apache Sling, Sling, Apache, the Apache feather logo, and
the Apache Sling project logo are trademarks of The Apache Software Foundation.
All other marks mentioned may be trademarks or registered trademarks of their
respective owners.
</p><p>
