jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-811) SetPropertyAssumeTypeTest check for non-protected string array property
Date Thu, 20 Sep 2007 18:11:31 GMT

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

Jukka Zitting updated JCR-811:
------------------------------

    Affects Version/s: 1.2.1
                       1.2.2
                       1.2.3
                       1.3
                       1.3.1
        Fix Version/s: 1.3.2

Merged to the 1.3 branch in revision 577845.

> SetPropertyAssumeTypeTest check for non-protected string array property
> -----------------------------------------------------------------------
>
>                 Key: JCR-811
>                 URL: https://issues.apache.org/jira/browse/JCR-811
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: JCR TCK
>    Affects Versions: 1.2.1, 1.2.2, 1.2.3, 1.3, 1.3.1
>            Reporter: Julian Reschke
>            Assignee: Julian Reschke
>            Priority: Minor
>             Fix For: 1.3.2
>
>
> SetPropertyAssumeTypeTest.testValuesConstraintViolationExceptionBecauseOfInvalidTypeParameter
tries to find a property definition for a writable, multivalued string property. It consults
NodeTypeUtil.locatePropertyDef() for that purpose.
> In my setup, the property definition being returned is for jcr:valueConstraints, defined
on nt:propertyDefinition. Nodes of that type in turn can not be created on the test node,
thus the test fails already when trying to create the node.
> It seems the test suite tries to be too smart here. Can we change this so that the node
type and the property name are configuration parameters?

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


Mime
View raw message