[
https://issues.apache.org/jira/browse/OAK-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13486740#comment-13486740
]
angela edited comment on OAK-250 at 10/30/12 10:19 AM:
-------------------------------------------------------
no, i don't think so... if you enforce it on the commithook you will just
disable
any modification of protected items. the point about the protected items is that
they cannot be set using regular JCR write API but only using the dedicated
API methods (versioning, locking, access control and so forth)... if we move it
down to the oak-level, we have to expose all those special APIs on the oak-API
which we wanted to avoid in favor of having just a simple write API.
regarding your suggestion:
that's definitely wrong... the protection constraint is not limited to existing
items
but applies to regular write operations on any kind of item. please see section
"3.7.2.2 Protected" of the jcr specification.
regarding the exception:
i suspect that there are still bugs in the way the item definition is retrieved.
can you please create a test-case that demonstrate the failure and create a
separate issue for that? thanks.
was (Author: anchela):
no, i don't think so... if you enforce it on the commithook you will just
disable
any modification of protected items. the point about the protected items is that
they cannot be set using regular JCR write API but only using the dedicated
API methods (versioning, locking, access control and so forth)... if we move it
down to the oak-level, we have to expose all those special APIs on the oak-API
which we wanted to avoid in favor of having just a simple write API.
regarding your suggestion:
that's definitely wrong... the protection constraint is not limited to existing
items
but to any item.
regarding the exception:
i suspect that there are still bugs in the way the item definition is retrieved.
can you please create a test-case that demonstrate the failure and create a
separate issue for that? thanks.
> Enforce jcr constraints for 'protected' items
> ---------------------------------------------
>
> Key: OAK-250
> URL: https://issues.apache.org/jira/browse/OAK-250
> Project: Jackrabbit Oak
> Issue Type: Sub-task
> Components: jcr
> Reporter: angela
>
--
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
