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

[jira] Created: (JCR-1915) Node.setPrimaryNodeType should only redefine child-definitions that are not covered by the new effective nt

Node.setPrimaryNodeType should only redefine child-definitions that are not covered by the new effective nt
-----------------------------------------------------------------------------------------------------------

                 Key: JCR-1915
                 URL: https://issues.apache.org/jira/browse/JCR-1915
             Project: Jackrabbit
          Issue Type: Bug
          Components: jackrabbit-core
    Affects Versions: 1.5.0
            Reporter: angela
             Fix For: 1.6.0


NodeImpl.setPrimaryNodeType changes the primary node type of an node and resets the definition of child items if required. Currently all child items that are not part of the effective node type of the new primary type get their definition reset or are removed in case not matching definition is found.
>From my point of view this doesn't properly cope with mixin types present on the node: child items defined by any of the mixin node types present should probably not be touched (or removed).

I run into this while testing the latest 283 security changes and will try to provide a fix along with those changes.

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

[jira] Resolved: (JCR-1915) Node.setPrimaryNodeType should only redefine child-definitions that are not covered by the new effective nt

Posted by "angela (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JCR-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

angela resolved JCR-1915.
-------------------------

    Resolution: Fixed
      Assignee: angela

> Node.setPrimaryNodeType should only redefine child-definitions that are not covered by the new effective nt
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: JCR-1915
>                 URL: https://issues.apache.org/jira/browse/JCR-1915
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: jackrabbit-core
>    Affects Versions: 1.5.0
>            Reporter: angela
>            Assignee: angela
>             Fix For: 1.6.0
>
>
> NodeImpl.setPrimaryNodeType changes the primary node type of an node and resets the definition of child items if required. Currently all child items that are not part of the effective node type of the new primary type get their definition reset or are removed in case not matching definition is found.
> From my point of view this doesn't properly cope with mixin types present on the node: child items defined by any of the mixin node types present should probably not be touched (or removed).
> I run into this while testing the latest 283 security changes and will try to provide a fix along with those changes.

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