[jira] [Commented] (SLING-5534) Improve namespace handling
[ https://issues.apache.org/jira/browse/SLING-5534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15157516#comment-15157516 ] Carsten Ziegeler commented on SLING-5534: - I've removed all deprecated stuff from jcr.base, and changed the namespace handling. It's now only done when the bundle is registered, but not with every session. I think, as Stefan points out above, the namespace handling could need some more improvements > 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 > 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)
[jira] [Commented] (SLING-5534) Improve namespace handling
[ https://issues.apache.org/jira/browse/SLING-5534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15155687#comment-15155687 ] Stefan Seifert commented on SLING-5534: --- it think we do no longer need here the alternative registration as _new if a mapping with the desired prefix already exists - this is unexpected behavior. instead we should just log an error if there is already a prefix with the same name which points to another namespace than the desired one. > 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 > 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)
[jira] [Commented] (SLING-5534) Improve namespace handling
[ https://issues.apache.org/jira/browse/SLING-5534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15153928#comment-15153928 ] Stefan Seifert commented on SLING-5534: --- yes, this came to my mind as well in context of SLING-5531 > 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 > Fix For: JCR Base 2.3.2 > > > 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)
