[ https://issues.apache.org/jira/browse/SLING-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12605013#action_12605013 ]
Eric Norman commented on SLING-522: ----------------------------------- I encountered this issue as well. My solution was basically the same as has been described in the comments. I scanned the primary type and mixin types to find a matching property definition and use the definition to provide defaults for the property type and for determining if the property is multi-valued. I'll attach a patch with my changes. > 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.