jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julian Reschke (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-741) Handling of multiple residual prop defs in EffectiveNodeTypeImpl
Date Tue, 06 Mar 2007 14:31:24 GMT

    [ https://issues.apache.org/jira/browse/JCR-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478423
] 

Julian Reschke commented on JCR-741:
------------------------------------

I think this will work for me; I'll try to adapt EffectiveNodeTypeImpl accordingly.

The fact that getPropertyDefinition() and getNodeDefinition() need to work on not-yet existing
items probably should be added to the Javadoc, it may not be obvious to everybody...


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


Mime
View raw message