[
https://issues.apache.org/jira/browse/SLING-5534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-5534.
-------------------------------------
Resolution: Fixed
Assignee: Carsten Ziegeler
I've simplified the namespace handling. If a mapping for the uri is already
available, or a mapping with the prefix, this is only logged as a warning
> Improve namespace handling
> --------------------------
>
> Key: SLING-5534
> URL: https://issues.apache.org/jira/browse/SLING-5534
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: JCR Base 2.4.0
>
> Attachments: patch.txt
>
>
> Right now the namespace handling support requries a proxy of the session
> object (in order to have namespace handling for impersonated session).
> In addition for each new session, the mapping code is run, although it should
> only run once and register the namespaces in the registry.
> This should improve performance as we don't have to run the namespace
> handling code for each and every session and get rid of the proxy.
> The namespace registration itself gets a little more tricky, but basically we
> can directly change the registry whenever a bundle with a namespace header
> arrives. We just need to think about collition handling
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
