[
https://issues.apache.org/jira/browse/OAK-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13608944#comment-13608944
]
Marcel Reutegger commented on OAK-713:
--------------------------------------
Is this somewhere backed in the specification?
I think in the case you are seeing, the correct behavior is indeed to *not*
convert the type, but rather identify another property definition, which may
match. E.g. there may be a residual property definition. AFAIK this is what the
current Jackrabbit implementation does. I'd suggest Oak behaves the same for
backward compatibility, unless the specification explicitly tells otherwise. In
this case we should probably also adjust the current Jackrabbit implementation.
> Automatic property type conversion
> ----------------------------------
>
> Key: OAK-713
> URL: https://issues.apache.org/jira/browse/OAK-713
> Project: Jackrabbit Oak
> Issue Type: Sub-task
> Components: core, jcr
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Priority: Minor
>
> It would be nice if, instead of throwing a validation error, Oak could
> automatically do basic property type conversions that lose no content. For
> example a single value could automatically be transformed to a multi-valued
> property when required by the matching property definition.
--
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
