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] Commented: (JCR-811) SetPropertyAssumeTypeTest check for non-protected string array property
Date Fri, 13 Apr 2007 07:05:17 GMT

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

Jukka Zitting commented on JCR-811:

Agreed. Using configuration parameters sounds good to me.

> 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
>            Reporter: Julian Reschke
>         Assigned To: Julian Reschke
>            Priority: Minor
> 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.

View raw message