You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2009/10/02 08:13:23 UTC

[jira] Resolved: (JCRTCK-17) Ambiguous exception conditions in version tests

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

Marcel Reutegger resolved JCRTCK-17.
------------------------------------

    Resolution: Fixed

Fixed in trunk in revision: 820894

> Ambiguous exception conditions in version tests
> -----------------------------------------------
>
>                 Key: JCRTCK-17
>                 URL: https://issues.apache.org/jira/browse/JCRTCK-17
>             Project: Jackrabbit JCR Tests
>          Issue Type: Bug
>            Reporter: Marcel Reutegger
>            Priority: Minor
>
> Both testSetProperty methods in VersionHistoryTest and VersionTest use the testRootNode as a parameter even though it is not referenceable. This leads to an ambiguous exception condition where an implementation may either throw a ValueFormatException (because the node is not referenceable) or a ConstraintViolationException (because the node is protected). The tests should rather use a referenceable node instead to avoid this situation.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.