jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Guggisberg (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-2143) Registering a Nodetype based on an existing NodeType fail
Date Thu, 11 Jun 2009 15:09:07 GMT

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

Stefan Guggisberg resolved JCR-2143.
------------------------------------

    Resolution: Fixed

fixed in svn r783809

> Registering a Nodetype based on an existing NodeType fail
> ---------------------------------------------------------
>
>                 Key: JCR-2143
>                 URL: https://issues.apache.org/jira/browse/JCR-2143
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>    Affects Versions: 1.5.6, 2.0-alpha1
>            Reporter: Luca Tagliani
>
> If I create a new NodeTypeTemplate using the code show below,
>            NodeTypeManagerImpl ntm = (NodeTypeManagerImpl) session.getWorkspace().getNodeTypeManager();
>            NodeTypeDefinition nt = (NodeTypeDefinition) ntm.getNodeType("wr:entity");
>            NodeTypeTemplate ntt = ntm.createNodeTypeTemplate(nt);
> the list of declaredSuperType contains the same name of the original nodeType (repeted
twice) and not the declaredSuperType of the original nodeType (in this example [nt:base, nt:file])
>           ntt.getDeclaredSupertypeNames(); -> [wr:entity, wr:entity]

-- 
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