You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2008/02/16 11:57:07 UTC
[jira] Resolved: (JCR-1390) TCK does not allow diverse Value types
in setProperty
[ https://issues.apache.org/jira/browse/JCR-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting resolved JCR-1390.
--------------------------------
Resolution: Invalid
Hmm, in fact there is a justification in the spec for this behaviour.
"All Value objects in the array must be of the same type, otherwise a ValueFormatException is thrown."
Sorry about the noise, resolved as Invalid.
> 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.
Re: [jira] Resolved: (JCR-1390) TCK does not allow diverse Value
types in setProperty
Posted by Julian Reschke <ju...@gmx.de>.
Jukka Zitting (JIRA) wrote:
> [ https://issues.apache.org/jira/browse/JCR-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Jukka Zitting resolved JCR-1390.
> --------------------------------
>
> Resolution: Invalid
>
> Hmm, in fact there is a justification in the spec for this behaviour.
>
> "All Value objects in the array must be of the same type, otherwise a ValueFormatException is thrown."
>
> Sorry about the noise, resolved as Invalid.
> ...
Proposal: new TCK tests (-> JSR-283) optimally should link to the spec
that holds the requirement that is being tested. Optimally *hyper*link.
See <https://jsr-283.dev.java.net/issues/show_bug.cgi?id=230>.
BR, Julian