[
https://issues.apache.org/jira/browse/SLING-5531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15153922#comment-15153922
]
Stefan Seifert commented on SLING-5531:
---------------------------------------
just tested this again - yes nodetype registration was working with 2.3.0. root
case for the wrong testcase initially was that restarting the jcr.base bundle
itself has not effect and does not lead to re-checking deployed bundle headers
- because it contains only abstract classes, and they are only reloaded if the
consuming bundle like oak-server are restarted.
will update the ticket title and apply the patch.
> 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
>
> Attachments: AbstractSlingRepository2.patch
>
>
> 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)
