You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2012/10/26 12:47:11 UTC

[jira] [Created] (OAK-406) RepositoryTest#testUniqueness should be moved to oak-level

angela created OAK-406:
--------------------------

             Summary: RepositoryTest#testUniqueness should be moved to oak-level
                 Key: OAK-406
                 URL: https://issues.apache.org/jira/browse/OAK-406
             Project: Jackrabbit Oak
          Issue Type: Bug
          Components: jcr
            Reporter: angela


RepositoryTest#testUniqueness attempts to verify that uniqueness
of jcr:uuid is properly enforced... however it does so by manually
setting the jcr:uuid which is protected and cannot be set using
regular jcr write operations.

this test should IMO be moved to oak-level including asserting that
the jcr:uuid uniqueness was actually part of the repo configuration

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

[jira] [Resolved] (OAK-406) RepositoryTest#testUniqueness should be moved to oak-level

Posted by "angela (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OAK-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

angela resolved OAK-406.
------------------------

    Resolution: Fixed
      Assignee: angela
    
> RepositoryTest#testUniqueness should be moved to oak-level
> ----------------------------------------------------------
>
>                 Key: OAK-406
>                 URL: https://issues.apache.org/jira/browse/OAK-406
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: jcr
>            Reporter: angela
>            Assignee: angela
>
> RepositoryTest#testUniqueness attempts to verify that uniqueness
> of jcr:uuid is properly enforced... however it does so by manually
> setting the jcr:uuid which is protected and cannot be set using
> regular jcr write operations.
> this test should IMO be moved to oak-level including asserting that
> the jcr:uuid uniqueness was actually part of the repo configuration

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