You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2015/08/10 08:14:45 UTC
[jira] [Created] (SLING-4937) Drop namespace mapping support
Carsten Ziegeler created SLING-4937:
---------------------------------------
Summary: Drop namespace mapping support
Key: SLING-4937
URL: https://issues.apache.org/jira/browse/SLING-4937
Project: Sling
Issue Type: Improvement
Components: JCR
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
Fix For: JCR Base 2.3.0
I think we should support the support for namespace mapping from our jcr
base module (and therefore from the jcr server implementations).
The namespace support parses the Sling-Namespaces header of bundles and
ensures that every session has namespace prefix mapping based on these
headers ensuring a stable mapping. The main reason why we added this in
the first place is, is that in theory one could map e.g. the sling
namespace prefix to some own non Sling url. Which obviously would break
all applications. Of course, no one really does this and even with this
mapping behavuĂour in place, I'm pretty sure apps would break if someone
does crazy mappings as we only cover the part where the Sling API is
used. Defaulting to the JCR API will probably use the wrong mapping.
As implementing this mapping creates proxy objects for the session which
is kind of heavy and I really think that this feature was never really
useful, I think we should drop it.
We can do this in a backwards compatible way by adding a new
AbstractSlingRepository3 base class.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)