You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by kw...@apache.org on 2021/07/24 09:33:43 UTC
[sling-site] branch master updated: SLING-9502 document pitfalls of
using the installer-provider-installhook (#47)
This is an automated email from the ASF dual-hosted git repository.
kwin pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-site.git
The following commit(s) were added to refs/heads/master by this push:
new c52e252 SLING-9502 document pitfalls of using the installer-provider-installhook (#47)
c52e252 is described below
commit c52e2527dbd9de2ba13a7cf5e36e6a0a85dceb80
Author: Konrad Windszus <kw...@apache.org>
AuthorDate: Sat Jul 24 11:33:34 2021 +0200
SLING-9502 document pitfalls of using the installer-provider-installhook (#47)
---
.../bundles/installer-provider-installhook.md | 14 +++++++++++---
1 file changed, 11 insertions(+), 3 deletions(-)
diff --git a/src/main/jbake/content/documentation/bundles/installer-provider-installhook.md b/src/main/jbake/content/documentation/bundles/installer-provider-installhook.md
index 33668a5..f76b343 100644
--- a/src/main/jbake/content/documentation/bundles/installer-provider-installhook.md
+++ b/src/main/jbake/content/documentation/bundles/installer-provider-installhook.md
@@ -4,15 +4,23 @@ status=published
tags=installer
~~~~~~
-## Overview
+# Background
+Content packages may contain OSGi bundles/configuration which are picked up asynchronously by the [JCR Installer Provider](jcr-installer-provider.html). That means that after the installation of a package the contained bundle/configuration is usually not yet installed.
-The Installer Vault Package Install Hook allows to install bundles and configurations synchronously during vault package installation by feeding them directly to the [OSGI Installer core](/documentation/bundles/osgi-installer.html). That way [vault package dependencies](http://jackrabbit.apache.org/filevault/properties.html) can be used to not only depend on content of a package, but also on configurations and bundles contained in a package (the installer install hook has to be added to [...]
+# Overview
+
+The Installer FileVault Package Install Hook allows to install bundles and configurations synchronously during FileVault/content package installation by feeding them directly to the [OSGI Installer core](/documentation/bundles/osgi-installer.html). That way [FileVault package dependencies](http://jackrabbit.apache.org/filevault/properties.html) can be used to not only depend on content of a package, but also on configurations and bundles contained in a package (the installer install hook [...]
NOTE: When using with a package that should be usable with both the [Feature Model](https://sling.apache.org/documentation/development/feature-model.html) (usually without the [OSGi Installer](https://sling.apache.org/documentation/bundles/osgi-installer.html)) and [Provisioning Model](https://sling.apache.org/documentation/development/slingstart.html) (usually with the OSGi Installer), ensure you use version 1.1.0 of this hook that will auto-detect its environment and only become active [...]
## Installation Process
-The Installer Vault Package Install Hook scans through the contained files and installs bundles (extension `jar`) and OSGi configurations with extension `config` (`conf` and node configurations are not supported). Runmode folders (e.g. `install.publish` or `config.author`) are supported. To perform the installation, the hook registers the installable resources to the OSGi installer core with the exact same digest as the JCR installer would do (hence the JCR installer that will also proce [...]
+The Installer Vault Package Install Hook scans through the contained files and installs bundles (extension `jar`) and OSGi configurations with extension `config` (`conf` and node configurations are not supported). Runmode folders (e.g. `install.publish` or `config.author`) are supported. To perform the installation, the hook registers the installable resources to the OSGi installer core with the exact same digest as the JCR installer would do (hence the JCR installer that will also proce [...]
+
+## Pitfalls
+
+In some cases a synchronous OSGi installer task leads to unavailability of the method by which the package has been provided (like the [Composum Package Manager](https://www.composum.com/home/nodes/pckgmgr.html)]. This is often caused by the fact that the [Dynamic Class Loader Provider restarts due to newly provided bundles](https://lists.apache.org/thread.html/57d56e31da3c1cb743cf524e0c85e46959f3af9ed946f2c4a41d33c0@%3Cdev.sling.apache.org%3E) or the whole Sling Repository restarts due [...]
+
## Configuration