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-1390) TCK does not allow diverse Value types in setProperty
Date Sat, 16 Feb 2008 10:23:08 GMT

    [ https://issues.apache.org/jira/browse/JCR-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569523#action_12569523

Jukka Zitting commented on JCR-1390:

The behaviour is unspecified, and so I think implementations should be free to choose how
to treat mixed multivalues.

As for JSR 283, it might make sense to explicitly allow mixed values. If an explicit target
type is given either in the method call or in a property definition, then all the values should
be converted to that type. Otherwise a default conversion to STRING probably makes most sense,
but I'd be fine also to leave the default behaviour unspecified. I'll follow up in the JSR
283 expert group on that.

> TCK does not allow diverse Value types in setProperty
> -----------------------------------------------------
>                 Key: JCR-1390
>                 URL: https://issues.apache.org/jira/browse/JCR-1390
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: jackrabbit-jcr-tests
>    Affects Versions: 1.3, 1.3.1, 1.3.3, 1.4
>            Reporter: Jukka Zitting
>            Priority: Minor
> I don't see the JCR API justifying the following test cases in SetPropertyValueTest:
>     testSetMixedValueArrayValueFormatException
>     testSetMixedValueArrayValueFormatExceptionWithPropertyType
> I propose to remove those tests.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message