You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2019/09/13 07:31:00 UTC
[jira] [Closed] (JCRVLT-336) FSPackageRegistry should allow forced
application scoping of PackageInstallations
[ https://issues.apache.org/jira/browse/JCRVLT-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Windszus closed JCRVLT-336.
----------------------------------
> 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üß
> Assignee: Tobias Bocanegra
> Priority: Major
> Fix For: 3.4.0
>
>
> 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
(v8.3.2#803003)