jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-2587) Coarser granularity of node type unregistration notifications
Date Fri, 26 Mar 2010 16:08:27 GMT

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

Jukka Zitting resolved JCR-2587.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 2.1.0

Fixed in revision 927945.

> Coarser granularity of node type unregistration notifications
> -------------------------------------------------------------
>
>                 Key: JCR-2587
>                 URL: https://issues.apache.org/jira/browse/JCR-2587
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-core, nodetype
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>            Priority: Minor
>             Fix For: 2.1.0
>
>
> When unregistering multiple node types at a time, the internal notification methods are
called separately for each type. This causes some problems as the first notifications triggers
the regeneration of the full virtual node type tree, and later notification calls will fail
(logging an error) in VirtualNodeTypeStateManager because the removed type is no longer there.
A better approach would be to send the names of all the unregistered node types as a collection.

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


Mime
View raw message