[JCR-811] SetPropertyAssumeTypeTest check for non-protected string array property

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.2.1, 1.2.2, 1.2.3, 1.3, 1.3.1
• Fix Version/s: 1.3.3
• Component/s: jackrabbit-jcr-tests
• Assignee: Julian Reschke
• Reporter: Julian Reschke
• Created: 22/Mar/07 15:52
• Updated: 08/Oct/07 10:47
• Resolved: 15/Aug/07 17:12

Description

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?