You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2013/02/28 14:47:17 UTC

[jira] [Assigned] (SLING-2761) JcrResourceProvider.create should filter protected properties

     [ https://issues.apache.org/jira/browse/SLING-2761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger reassigned SLING-2761:
----------------------------------------

    Assignee: Carsten Ziegeler

Thanks for the update.

It looks like the introduction of CRUD for the Resource API and the respective conversion of the JCR support did not properly account for protected properties. Particularly I think, the JCR based ResourceProvider implementation should account for the following:

  * ResourceProvider.create to should filter the properties
  * ModifiableValueMap.put should filter the properties

I would assume that the jcr:primaryType and jcr:mixinTypes properties should be mapped to the respective setters.

Carsten can you take care of this ? Thanks.
                
> JcrResourceProvider.create should filter protected properties
> -------------------------------------------------------------
>
>                 Key: SLING-2761
>                 URL: https://issues.apache.org/jira/browse/SLING-2761
>             Project: Sling
>          Issue Type: Bug
>          Components: Testing
>            Reporter: Alex Parvulescu
>            Assignee: Carsten Ziegeler
>
> While running some of the integration tests using Oak as a repository impl, I ran into some ConstraintViolationExceptions with the PostServletVersionableTest.
> This uncovered an issue in Jackrabbit JCR-3526 where you can change protected properties on new items, which is in fact considered illegal.
> Coming back to the PostServletVersionableTest, the test setup uses this trick to set up the content and I think it should be changed.
> On a more general note fixing JCR-3526 could turn up even more problems that the aforementioned test, so it would be nice to have some more thoughts on this on how big the problem could really be.

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