[
https://jira.jboss.org/jira/browse/DNA-344?page=com.atlassian.jira.plugin...
]
Brian Carothers updated DNA-344:
--------------------------------
Attachment: DNA-344_no_extra_conversion.patch
Uploaded a second patch (delta from the first) that removes the now-extraneous extra
conversion in JcrValue.asType. Since JcrSession.getValueFactory.create(String, int) now
eagerly converts the given value to the appropriate native type, our JcrValues should
always have a native type that corresponds to their JCR PropertyType.
All dna-jcr tests still pass.
JcrSession.getValueFactory.create(String, int) Does Not Fail Fast as
per Specification
--------------------------------------------------------------------------------------
Key: DNA-344
URL:
https://jira.jboss.org/jira/browse/DNA-344
Project: DNA
Issue Type: Bug
Components: JCR
Affects Versions: 0.4
Reporter: Brian Carothers
Attachments: DNA-344.patch, DNA-344_no_extra_conversion.patch
Section 7.1.5.3 of the JCR 1.0.1 specification (pg 199) indicates that
ValueFactory.create(String value, int propertyType) should throw a ValueFormatException if
value cannot be converted to the correct type. We currently defer all casts of the value
and do not fail fast.
This prevents one of the test cases in the L2 TCK test ValueFactoryTest from passing
successfully.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira