[
https://issues.apache.org/jira/browse/OAK-823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660538#comment-13660538
]
Jukka Zitting commented on OAK-823:
-----------------------------------
As Alex noted on oak-dev@, using the validator to prevent all modifications to
jcr:uuid properties is troublesome. Instead the validator should just check
that the jcr:uuid value is always valid, regardless of how it got set. I
adjusted the code accordingly in http://svn.apache.org/r1483721.
> Missing validation for jcr:uuid property
> ----------------------------------------
>
> Key: OAK-823
> URL: https://issues.apache.org/jira/browse/OAK-823
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core
> Reporter: angela
> Assignee: angela
>
> A jcr:uuid property (defined by mix:referenceable) is defined to be
> an autocreated/mandatory/protected property.
> Currently the commit hooks don't make sure that in this case
> - the value is a valid UUID (propertyAdded)
> - nor does it assert that this property can never be modified
> (propertyChanged)
> note however, that i might be removed in case the mixin type is removed or
> the primary type gets modified and there is no valid definition left for
> that property. since the type-validator must assert that the mandatory
> property exists (if the node is referenceable) there is not extra verification
> needed in the case of removal.
--
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
