[
https://issues.apache.org/jira/browse/JCR-3600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luca Tagliani updated JCR-3600:
-------------------------------
Status: Patch Available (was: Open)
Adding a patch for using also the requiredPrimaryTypeNames as a comparison
criteria between two child definition id.
> Error adding a new child definition to a nodeType with the same name but
> different requiredPrimareTypeNames using API
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: JCR-3600
> URL: https://issues.apache.org/jira/browse/JCR-3600
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-spi-commons
> Affects Versions: 2.6.1
> Reporter: Luca Tagliani
> Attachments: JCR-3600.patch
>
>
> I want to register a new child definition under an existing nodetype.
> This nodetype has yet a child definition with the same name but different
> requiredPrimaryTypeName.
> The NodeTypeDefDiff identify this modification as MAJOR.
> This happens because the code of buildChildNodeDefDiffs method use a
> QNodeDefinitionId constructor that only uses the declaringNodeType and name
> (that obviously are the same for the two child definitions).
> So, when the algorithm test the difference between the old child definitions
> and the new child definitions finds that the existing child definition is
> modified (currently the requiredPrimaryNodeType).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
