You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2012/06/22 16:29:42 UTC

[jira] [Resolved] (OAK-149) Automatic session refresh after namespace registry changes

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

Jukka Zitting resolved OAK-149.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 0.3

In fact the session should be automatically refreshed whenever the namespace registry is explicitly accessed, be it for read or write. That way the client has a consistent view of the repository at all times.

Done in revision 1352901.
                
> Automatic session refresh after namespace registry changes
> ----------------------------------------------------------
>
>                 Key: OAK-149
>                 URL: https://issues.apache.org/jira/browse/OAK-149
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: jcr
>            Reporter: Jukka Zitting
>            Priority: Minor
>             Fix For: 0.3
>
>
> The registerNamespace() and unregisterNamespace() methods of NamespaceRegistry should cause the session from which the registry instance was acquired to refresh its state. Otherwise code that first registers a new namespace and then tries to use it might end up failing because the session is still seeing and older version of the content tree. Potential other sessions should remain as they are and only start seeing the modified namespaces once they're separately refreshed.
> PS. Similar refresh requirements probably also affect things like node type registration, versioning, direct-to-workspace writes, etc.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira