You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Eric Norman (JIRA)" <ji...@apache.org> on 2009/02/09 01:20:59 UTC
[jira] Commented: (SLING-534) Multi-Value Reference properties are
not exposed to scripting the same way as single-value reference properties
[ https://issues.apache.org/jira/browse/SLING-534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671704#action_12671704 ]
Eric Norman commented on SLING-534:
-----------------------------------
Is there anything keeping this patch from being committed?
> Multi-Value Reference properties are not exposed to scripting the same way as single-value reference properties
> ---------------------------------------------------------------------------------------------------------------
>
> Key: SLING-534
> URL: https://issues.apache.org/jira/browse/SLING-534
> Project: Sling
> Issue Type: Bug
> Components: Scripting JavaScript (Rhino)
> Affects Versions: Scripting JavaScript 2.0.2
> Reporter: Eric Norman
> Attachments: multival_refprops_lookup.diff, SLING-534-fmeschbe.patch, unit_test.diff
>
>
> If a node contains a multi-valued reference property, it is exposed to scripts as an array of UUID strings. For single-value reference properties the value is resolved to the referenced node. I'd expect the multi-value reference properties to be resolved the same way and exposed to scripting as an array of nodes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.