[
https://issues.apache.org/jira/browse/JCR-639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13006500#comment-13006500
]
Alexander Klimetschek commented on JCR-639:
-------------------------------------------
Since it came up on the mailing list: The JCR 2.0 spec defines this as standard
behavior. Section 15.2.2:
"When a node N becomes read-only: No property of N can be added, removed or
have its value changed unless it has an on-parent-version setting of IGNORE."
http://www.day.com/specs/jcr/2.0/15_Versioning.html#15.2.2%20Read-Only%20on%20Check-In
> Allow modification of OPV=IGNORE items even if parent node is checked-in.
> -------------------------------------------------------------------------
>
> Key: JCR-639
> URL: https://issues.apache.org/jira/browse/JCR-639
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core, versioning
> Affects Versions: 0.9, 1.0, 1.0.1, 1.1
> Reporter: Tobias Bocanegra
>
> currently jackrabbit does not allow to modify OPV=IGNORE items if the parent
> node is checked in. since they are excluded from the frozen state of the
> version, this should/could be allowed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
