[SLING-4937] Drop per session namespace mapping support

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: JCR Jackrabbit Server 2.3.0, JCR Base 2.3.0, JCR Oak Server 1.0.0
• Component/s: JCR
• Assignee: Carsten Ziegeler
• Reporter: Carsten Ziegeler
• Created: 10/Aug/15 06:14
• Updated: 18/Feb/16 06:17
• Resolved: 11/Aug/15 11:07

Description

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.

Issue Links

• relates to: SLING-5531 Sling-Namespaces bundle header for registering JCR namespaces broken