[JCR-3543] TCK does not allow a property to be re-bound to a different definition

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.6
• Fix Version/s: 2.6.2, 2.7
• Component/s: jackrabbit-jcr-tests
• Assignee: Jukka Zitting
• Reporter: Jukka Zitting
• Created: 26/Mar/13 06:54
• Updated: 21/May/13 09:02
• Resolved: 26/Mar/13 07:07

Description

The JCR spec says the following about Node.setProperty:

Some repositories may allow P to be dynamically re-bound to a different
property definition (based for example, on the new value being of a different
type than the original value) while other repositories may not allow such
dynamic re-binding.

However, the current TCK requires the implementation to keep the definition of the existing property.