You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2004/12/22 16:51:03 UTC
[jira] Created: (JCR-36) NodeTypeRegistry.reregister unregisters dependent types
NodeTypeRegistry.reregister unregisters dependent types
-------------------------------------------------------
Key: JCR-36
URL: http://nagoya.apache.org/jira/browse/JCR-36
Project: Jackrabbit
Type: Bug
Environment: Jackrabbit SVN Rev. 122969
Reporter: Felix Meschberger
Priority: Critical
NodeTypeRegistry.reregister allows modifying a registered node type if the difference to the currently registered node type with the same name is TRIVIAL according to NodeTypeDefDiff.
Before registering the new node type definition the old node type is unregistered. The side effect of that first step is that also all NodeTypes, which depend (extend ?) the node type to be re-registered, are removed from the registry.
After the modified node type is then registered, the previously registered dependent node types will not be registered anymore and will not be known any more.
While it makes sense to me, to temporarily unregister dependent node types, those must be registered again after the re-registered node type has been registered. Otherwise the system may become pretty useless.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Closed: (JCR-36) NodeTypeRegistry.reregister unregisters dependent types
Posted by "Stefan Guggisberg (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-36?page=history ]
Stefan Guggisberg closed JCR-36:
--------------------------------
> NodeTypeRegistry.reregister unregisters dependent types
> -------------------------------------------------------
>
> Key: JCR-36
> URL: http://issues.apache.org/jira/browse/JCR-36
> Project: Jackrabbit
> Type: Bug
> Environment: Jackrabbit SVN Rev. 122969
> Reporter: Felix Meschberger
> Assignee: Stefan Guggisberg
> Priority: Critical
>
> NodeTypeRegistry.reregister allows modifying a registered node type if the difference to the currently registered node type with the same name is TRIVIAL according to NodeTypeDefDiff.
> Before registering the new node type definition the old node type is unregistered. The side effect of that first step is that also all NodeTypes, which depend (extend ?) the node type to be re-registered, are removed from the registry.
> After the modified node type is then registered, the previously registered dependent node types will not be registered anymore and will not be known any more.
> While it makes sense to me, to temporarily unregister dependent node types, those must be registered again after the re-registered node type has been registered. Otherwise the system may become pretty useless.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Resolved: (JCR-36) NodeTypeRegistry.reregister unregisters dependent types
Posted by "Stefan Guggisberg (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-36?page=history ]
Stefan Guggisberg resolved JCR-36:
----------------------------------
Resolution: Fixed
fixed in r123983
> NodeTypeRegistry.reregister unregisters dependent types
> -------------------------------------------------------
>
> Key: JCR-36
> URL: http://issues.apache.org/jira/browse/JCR-36
> Project: Jackrabbit
> Type: Bug
> Environment: Jackrabbit SVN Rev. 122969
> Reporter: Felix Meschberger
> Assignee: Stefan Guggisberg
> Priority: Critical
>
> NodeTypeRegistry.reregister allows modifying a registered node type if the difference to the currently registered node type with the same name is TRIVIAL according to NodeTypeDefDiff.
> Before registering the new node type definition the old node type is unregistered. The side effect of that first step is that also all NodeTypes, which depend (extend ?) the node type to be re-registered, are removed from the registry.
> After the modified node type is then registered, the previously registered dependent node types will not be registered anymore and will not be known any more.
> While it makes sense to me, to temporarily unregister dependent node types, those must be registered again after the re-registered node type has been registered. Otherwise the system may become pretty useless.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Assigned: (JCR-36) NodeTypeRegistry.reregister unregisters dependent types
Posted by "Stefan Guggisberg (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-36?page=history ]
Stefan Guggisberg reassigned JCR-36:
------------------------------------
Assign To: Stefan Guggisberg
> NodeTypeRegistry.reregister unregisters dependent types
> -------------------------------------------------------
>
> Key: JCR-36
> URL: http://issues.apache.org/jira/browse/JCR-36
> Project: Jackrabbit
> Type: Bug
> Environment: Jackrabbit SVN Rev. 122969
> Reporter: Felix Meschberger
> Assignee: Stefan Guggisberg
> Priority: Critical
>
> NodeTypeRegistry.reregister allows modifying a registered node type if the difference to the currently registered node type with the same name is TRIVIAL according to NodeTypeDefDiff.
> Before registering the new node type definition the old node type is unregistered. The side effect of that first step is that also all NodeTypes, which depend (extend ?) the node type to be re-registered, are removed from the registry.
> After the modified node type is then registered, the previously registered dependent node types will not be registered anymore and will not be known any more.
> While it makes sense to me, to temporarily unregister dependent node types, those must be registered again after the re-registered node type has been registered. Otherwise the system may become pretty useless.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira