[ https://issues.apache.org/jira/browse/SLING-5531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15151956#comment-15151956 ]
Carsten Ziegeler commented on SLING-5531: ----------------------------------------- [~sseif...@pro-vision.de] It's still there, AbstractSlingRepository extends NamespaceMappingSupport which should do the mapping AbstractSlingRepository2 use the manager which extends this as well. Looking at the changes of SLING-4937 I don't think that anything with respect to that has been removed - at least I can't find it. > Declared Node Type Registration support broken in JCR Base > ---------------------------------------------------------- > > Key: SLING-5531 > URL: https://issues.apache.org/jira/browse/SLING-5531 > Project: Sling > Issue Type: Bug > Components: JCR > Affects Versions: JCR Base 2.3.0 > Reporter: Stefan Seifert > Assignee: Carsten Ziegeler > Priority: Critical > Fix For: JCR Base 2.3.2 > > > the changes for SLING-4937 (Drop namespace mapping support) broke the > "Declared Node Type Registration" feature described in [1]. > this allows to register custom JCR namespaces or nodetypes via a CND file > when deploying a bundle and specifying the CND file via a {{Sling-Nodetypes}} > bundle header. > i assume only the support for {{Sling-Namespaces}} should be removed with > SLING-4937, not the support for {{Sling-Nodetypes}}. > [1] > https://sling.apache.org/documentation/bundles/content-loading-jcr-contentloader.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)