[
https://issues.apache.org/jira/browse/JCR-811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke resolved JCR-811.
--------------------------------
Resolution: Fixed
This resolves the issue for my use cases. However there may be some other
scenarios where the strategy of picking a random property type may prove
problematic.
> 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
> Assignee: 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.
