[
https://issues.apache.org/jira/browse/SLING-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604897#action_12604897
]
Carsten Ziegeler commented on SLING-522:
----------------------------------------
The problem is the detection of the property definition - JCR does not provide
a method for this. So, in order to propertly implement this,
we have to scan the primary node type of a node, followed by all mixins etc. I
have the feeling that this is a costly operation compared to
the problem it might solve. I haven't looked at JCR 2.0 yet, if it provides
something in this area.
Therefore I would be very happy if you could live with the explicit hint for
now :)
> Default POST Servlet writes single-value property even though node type
> mandates multi-value.
> ---------------------------------------------------------------------------------------------
>
> Key: SLING-522
> URL: https://issues.apache.org/jira/browse/SLING-522
> Project: Sling
> Issue Type: Bug
> Components: Servlets Post
> Affects Versions: 2.0.1
> Reporter: Julian Sedding
> Priority: Minor
> Fix For: 2.1.0
>
>
> If a JCR node-type defines a multi-value property (e.g. String[]) and only a
> single value for this property is posted, the property will become
> single-value (e.g String). The POST Servlet should check, if the property is
> multi-value and respect that. Otherwise, any code reading the property value
> would need to check, whether it is multi-value or not and handle both cases.
> It might even be beneficial to force a multi-value property, if there is no
> node-type that defines it. This would provide for better control of
> unstructured data.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
