You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2007/07/12 21:10:05 UTC
[jira] Created: (JCR-1029) CLONE -Handling of multiple residual
prop defs in EffectiveNodeTypeImpl
CLONE -Handling of multiple residual prop defs in EffectiveNodeTypeImpl
-----------------------------------------------------------------------
Key: JCR-1029
URL: https://issues.apache.org/jira/browse/JCR-1029
Project: Jackrabbit
Issue Type: Bug
Components: SPI
Reporter: Julian Reschke
Assignee: 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.
[jira] Resolved: (JCR-1029) CLONE -Handling of multiple residual
prop defs in EffectiveNodeTypeImpl
Posted by "Julian Reschke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Reschke resolved JCR-1029.
---------------------------------
Resolution: Fixed
Fixed with revision 555992.
> CLONE -Handling of multiple residual prop defs in EffectiveNodeTypeImpl
> -----------------------------------------------------------------------
>
> Key: JCR-1029
> URL: https://issues.apache.org/jira/browse/JCR-1029
> Project: Jackrabbit
> Issue Type: Bug
> Components: SPI
> Reporter: Julian Reschke
> Assignee: 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.
[jira] Commented: (JCR-1029) CLONE -Handling of multiple residual
prop defs in EffectiveNodeTypeImpl
Posted by "Julian Reschke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512218 ]
Julian Reschke commented on JCR-1029:
-------------------------------------
The change for JCR-741 was lost in a recent refactoring.
> CLONE -Handling of multiple residual prop defs in EffectiveNodeTypeImpl
> -----------------------------------------------------------------------
>
> Key: JCR-1029
> URL: https://issues.apache.org/jira/browse/JCR-1029
> Project: Jackrabbit
> Issue Type: Bug
> Components: SPI
> Reporter: Julian Reschke
> Assignee: 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.
[jira] Updated: (JCR-1029) CLONE -Handling of multiple residual
prop defs in EffectiveNodeTypeImpl
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated JCR-1029:
-------------------------------
Fix Version/s: 1.4
> CLONE -Handling of multiple residual prop defs in EffectiveNodeTypeImpl
> -----------------------------------------------------------------------
>
> Key: JCR-1029
> URL: https://issues.apache.org/jira/browse/JCR-1029
> Project: Jackrabbit
> Issue Type: Bug
> Components: SPI
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Minor
> Fix For: 1.4
>
>
> 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.