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 2022/10/11 13:35:00 UTC
[jira] [Commented] (JCRVLT-663) Expose some API to create a JcrPackageRegistry/FSPackageRegistry
[ https://issues.apache.org/jira/browse/JCRVLT-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17615812#comment-17615812 ]
Konrad Windszus commented on JCRVLT-663:
----------------------------------------
[~dsuess] [~tripod] What is your opinion, how are those to be used outside OSGi?
> Expose some API to create a JcrPackageRegistry/FSPackageRegistry
> ----------------------------------------------------------------
>
> Key: JCRVLT-663
> URL: https://issues.apache.org/jira/browse/JCRVLT-663
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Reporter: Konrad Windszus
> Priority: Major
>
> Currently both {{JcrPackageRegistry}} and {{FSPackageRegistry}} are contained in the non-public package {{org.apache.jackrabbit.vault.packaging.registry.impl}}. That means that there is no way to create instances without relying on that internal package.
> Particularly creating ExecutionPlans is not easily possible outside an OSGi container.
> Example usages relying on the internal package are e.g. https://github.com/apache/sling-org-apache-sling-feature-extension-content/blob/4c7a202d8d972f6a1885bc1a6ea416c45ed53c95/src/main/java/org/apache/sling/feature/extension/content/ContentHandler.java#L73.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)