You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Seifert (JIRA)" <ji...@apache.org> on 2016/02/19 09:50:18 UTC

[jira] [Resolved] (SLING-5531) Sling-Namespaces bundle header for registering JCR namespaces broken

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

Stefan Seifert resolved SLING-5531.
-----------------------------------
    Resolution: Fixed

Completed: At revision: 1731199  


> Sling-Namespaces bundle header for registering JCR namespaces broken
> --------------------------------------------------------------------
>
>                 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)