You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Alex Parvulescu (JIRA)" <ji...@apache.org> on 2012/12/12 12:49:21 UTC
[jira] [Resolved] (JCR-3480) Extend
SaveTest#testConstraintViolationException to cover cases where the
validation happens on Session#save
[ https://issues.apache.org/jira/browse/JCR-3480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Parvulescu resolved JCR-3480.
----------------------------------
Resolution: Fixed
Fix Version/s: 2.5.3
fixed with rev 1420626.
> Extend SaveTest#testConstraintViolationException to cover cases where the validation happens on Session#save
> ------------------------------------------------------------------------------------------------------------
>
> Key: JCR-3480
> URL: https://issues.apache.org/jira/browse/JCR-3480
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-jcr-tests
> Reporter: Alex Parvulescu
> Assignee: Alex Parvulescu
> Fix For: 2.5.3
>
>
> The test is org.apache.jackrabbit.test.api.query.SaveTest located in jackrabbit-jcr-tests.
> The issue is that even thought the api allows for impelmentations that perform lazy validation (at a later Session#save call), the test assumes direct validation and therefore fails when running against Oak code.
> I'm proposing to add a Session#save call to the test to verify that the validation happens either directly or on the save call.
--
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