[
https://issues.apache.org/jira/browse/SLING-5531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert updated SLING-5531:
----------------------------------
Attachment: AbstractSlingRepository2.patch
i think i've found the problem.
the Loader is registered as bundle listener and nicely collects all bundle
headers with namespaces or node types (and logs this in DEBUG level, not sure
why i've not seen the messages in my previous attempt). but they never get
applied to a session and thus not to the JCR repository when
AbstractSlingRepository2 is used.
please see the patch [^AbstractSlingRepository2.patch]. with this patch the
namespace registration works as expected. but i have no good understanding of
the code in this module, [~cziegeler], can you have a look again?
> 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: Stefan Seifert
> 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)
