You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Karl Pauls (JIRA)" <ji...@apache.org> on 2019/07/02 15:12:00 UTC

[jira] [Updated] (SLING-8528) ACLs for Serviceusers on nodes with nodetypes registered via content-package may break startup in repoinit.

     [ https://issues.apache.org/jira/browse/SLING-8528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karl Pauls updated SLING-8528:
------------------------------
    Component/s:     (was: Feature Model)
                 Content-Package to Feature Model Converter

> ACLs for Serviceusers on nodes with nodetypes registered via content-package may break startup in repoinit.
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: SLING-8528
>                 URL: https://issues.apache.org/jira/browse/SLING-8528
>             Project: Sling
>          Issue Type: Bug
>          Components: Content-Package to Feature Model Converter
>            Reporter: Dominik Süß
>            Assignee: Simone Tripodi
>            Priority: Major
>
> If a content-package contains a CND with a new nodetype these nodetypes are processed and registered before the content is being installed. The CP to featuremodel converter creates paths for nodes on which ACLS for serviceusers are registered. These nodes may be created based on nodetypes defined in the own or another content-package it depends on.  
> As repoinit is executed ahead of content-package installation the execution of repoinit may fail with {{javax.jcr.nodetype.NoSuchNodeTypeException: Node type my:NodeType does not exist}} 
> To eliminate this problem altogether the converter should extract all node type definitions found in content-packages and registere via repoinit (see register nodetype section in https://sling.apache.org/documentation/bundles/repository-initialization.html)



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