[
https://issues.apache.org/jira/browse/JCR-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478345
]
Marcel Reutegger commented on JCR-741:
--------------------------------------
Hmm, if you have to do the call to the store anyway then I propose the
following:
- Keep the methods RepositoryService.getPropertyDefinition() and
RepositoryService.getNodeDefinition()
- Resolve the item definitions using the node type information whenever
possible.
- If there is a conflicting situation with multiple residual definitions that
match, ask the repository service for the correct one using
RepositoryService.getPropertyDefinition() or
RepositoryService.getNodeDefinition()
Does that work for you? Is there enough information in the parameters to decide
which definition to use? Please also note that those calls will use ids that
reference items that do not yet exist.
> Handling of multiple residual prop defs in EffectiveNodeTypeImpl
> ----------------------------------------------------------------
>
> Key: JCR-741
> URL: https://issues.apache.org/jira/browse/JCR-741
> Project: Jackrabbit
> Issue Type: Bug
> Components: SPI
> Reporter: Julian Reschke
> Assigned To: Julian Reschke
> Priority: Minor
>
> org.apache.jackrabbit.jcr2spi.nodetype.EffectiveNodeTypeImpl currently
> rejects multiple residual property definitions, if they do not differ in
> getMultiple(). In fact, it should accept all combinations, so differing
> values for getOnParentVersionAction and other aspects should be accepted as
> well.
> See JSR 170, 6.7.8:
> "For purposes of the above, the notion of two definitions having the same
> name does not apply to two residual definitions. Two (or more) residual
> property or child node definitions with differing subattributes must be
> permitted to co-exist in the same effective node type. They are interpreted
> as disjunctive (ORed) options."
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
