You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2008/10/19 01:50:44 UTC

[jira] Updated: (JCR-1612) Reintroduce NamespaceStorage

     [ https://issues.apache.org/jira/browse/JCR-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting updated JCR-1612:
-------------------------------

    Summary: Reintroduce NamespaceStorage  (was: Reintroduce NamespaceStorage and namespace-caching)

Hmm, revision 705932 caused a test failure so I reverted it in revision 705937.

In fact it seems impossible to do implement a repository-level namespace cache on top of the RepositoryService interface without making the assumption that namespace mappings are session-independent. This assumption is not supported by the RepositoryService design that has SessionInfo as an argument to all namespace methods, not only those where write authorization could be needed.

I know we agreed to reintroduce the cache, but should we reconsider based on the above observation? At least I suggest that we limit the scope of this issue to NamespaceStorage and, if there really is a need for the cache, open a separate issue to track the cache feature.

> Reintroduce NamespaceStorage
> ----------------------------
>
>                 Key: JCR-1612
>                 URL: https://issues.apache.org/jira/browse/JCR-1612
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: jackrabbit-jcr2spi
>            Reporter: angela
>            Assignee: Jukka Zitting
>             Fix For: 1.5.0
>
>
> hi jukka
> i open this issue as a reminder of our recent discussion in basel:
> we decided that you will 
> - reintroduce the NamespaceStorage you recently removed from jcr2spi
> - reintroduce a namespace cache in jcr2spi (but using a simple map instead of NamespaceCache object)
> in addition we agreed that we want to share the NamespaceRegistryImpl between jcr2spi and jackrabbit-core
> and you volenteered to provide a patch for that.
> thanks in advance
> angela

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.