You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Dominik Süß (JIRA)" <ji...@apache.org> on 2019/04/01 20:51:00 UTC

[jira] [Created] (JCRVLT-336) FSPackageRegistry should allow forced application scoping of PackageInstallations

Dominik Süß created JCRVLT-336:
----------------------------------

             Summary: FSPackageRegistry should allow forced application scoping of PackageInstallations
                 Key: JCRVLT-336
                 URL: https://issues.apache.org/jira/browse/JCRVLT-336
             Project: Jackrabbit FileVault
          Issue Type: Improvement
          Components: Packaging
            Reporter: Dominik Süß


In contrast to JCR Package Registry the installation of Packages via FS PackageRegistry is designed for application deployment procedures. As these installations are mostly hidden behind the implementation details of ExecutionPlan I propose the introduction of a flag that implicitly decorates the filter with the already existing ScopedFilter.

Although it is tempting to perform the same for application scoping on the JCR Registry the various ways to tricker package installations make it  harder to introduce a similar configuration that catches all scenarios - as ExecutionPlan is not a scenario for installation via PackageManager (the still dominant scenario of installing packages at runtime) - the consuming code may decorate and set the decorated workspaceFilter, making it an explicit choice of the consuming code.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)