[
https://issues.apache.org/jira/browse/SLING-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540716
]
Felix Meschberger commented on SLING-23:
----------------------------------------
Added the namespace mapping for Jackrabbit OCM and Sling to the bundle manifest
header of the jcr/resource project as follows:
<Sling-Namespaces>
sling=http://sling.apache.org/jcr/sling/1.0,
ocm=http://jackrabbit.apache.org/ocm
</Sling-Namespaces>
> Use correct namespaces (for node types, taglibs etc)
> ----------------------------------------------------
>
> Key: SLING-23
> URL: https://issues.apache.org/jira/browse/SLING-23
> Project: Sling
> Issue Type: Bug
> Components: API
> Reporter: Carsten Ziegeler
>
> As recently discussed, all namespace for sling should start with
> "http://sling.apache.org/"; (and not use the jackrabbit namespace), followed
> by an intermediate path denoting the type (like taglib, jcr namespace etc),
> followed by the version, so we'll have:
> http://sling.apache.org/taglibs/sling/1.0
> http://sling.apache.org/jcr/sling/1.0
> etc.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
