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] [Resolved] (JCR-3543) TCK does not allow a property to be re-bound to a different definition
Date Tue, 26 Mar 2013 07:09:15 GMT

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

Jukka Zitting resolved JCR-3543.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 2.7
         Assignee: Jukka Zitting

Fixed in revision 1460995.
                
> TCK does not allow a property to be re-bound to a different definition
> ----------------------------------------------------------------------
>
>                 Key: JCR-3543
>                 URL: https://issues.apache.org/jira/browse/JCR-3543
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-jcr-tests
>    Affects Versions: 2.6
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>            Priority: Minor
>             Fix For: 2.7
>
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message