Support for jcr namespace prefixes
----------------------------------
Key: SLING-86
URL: https://issues.apache.org/jira/browse/SLING-86
Project: Sling
Issue Type: New Feature
Components: Content
Reporter: Carsten Ziegeler
Namespace handling with jcr can become complicated as usually the application
is just using prefixes instead of the full namespace uri. Therefore the
application either has to make assumptions about the registered prefixes or has
to lookup the used prefixes. While the assumptions obviously can lead to
problems, the second solution is very hard and time consuming to implement.
Sling can help in this respect as it ensures that some prefixes point to the
correct namespace regardless of how they are registered in the repository. This
can be done by reassigning namespaces on a per session base.
The idea is that a bundle can have the "Sling-Namespaces" manifest entry which
can contain one or more definition for namespaces, like
Sling-Namespaces: sling=http://sling.apache.org/jcr/core/1.0
Sling will take care that these prefixes are mapped accordingly for each
session which is get through Sling. There an application based on Sling can
safely make the assumption about these namespace prefixes.
The manifest entries will be read on a bundle install event and updated on an
uninstall event.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
