[
https://issues.apache.org/jira/browse/SLING-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12931658#action_12931658
]
Julian Sedding commented on SLING-1859:
---------------------------------------
I don't know if this is a bug or not, but maybe you can work around your issue
like this (I'm writing java, but it should be possible to convert to esp):
ValueMap properties = ResourceUtil,getValueMap(resource); // guards against NPE
in this and in the next line
String[] property = properties.get(id, new String[0]); // not sure you want
strings, I guess you could also ask for Long[0] etc.
> Multi-value string properties are not displayed correctly
> ---------------------------------------------------------
>
> Key: SLING-1859
> URL: https://issues.apache.org/jira/browse/SLING-1859
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Affects Versions: Sling Explorer 1.0.0
> Reporter: Carsten Ziegeler
> Assignee: Mike Müller
>
> I have a node with a multi value string property, and the explorer displays
> the value as "[Ljava.lang.Object;@1a6b7e", together with the hint "[not a
> property!]
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
