[
https://issues.apache.org/jira/browse/OAK-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13608955#comment-13608955
]
Jukka Zitting commented on OAK-713:
-----------------------------------
The spec is pretty relaxed about [applicable item
definitions|http://www.day.com/specs/jcr/2.0/3_Repository_Model.html#3.7.7
Applicable Item Definition]:
bq. Though there may be more than one definition in the parent node's type that
could apply to the child item, the definition that does apply is determined by
the implementation and remains constant through the lifetime of the item.
However, in practice I find the Jackrabbit behavior quite troublesome. Taken to
the extreme it would allow a jcr:primaryType property of an nt:unstructured
node to be a multi-valued binary property.
Instead my idea in OAK-411 is to always use a matching *named* definition when
available, and fall back to residual definitions only when a named definition
is not found. This should also be better in line with what a typical user would
expect.
The motivation for this issue, automatic type conversion, comes from the desire
to automatically and gracefully provide backwards compatibility to clients and
content from Jackrabbit deployments.
> 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
