[
https://issues.apache.org/jira/browse/SLING-7515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389437#comment-16389437
]
Konrad Windszus edited comment on SLING-7515 at 3/7/18 11:42 AM:
-----------------------------------------------------------------
The problem with the {{requestAttributes}} option is, that this requires a Map.
Unfortunately the HTL expression language does not know map literals. Therefore
I would like to have one option per attribute which I can express perfectly
fine in HTL only (without being forced to rely on some backing Java model).
was (Author: kwin):
The problem with the `requestAttributes` option is, that this requires a Map.
Unfortunately the HTL expression language does not know map literals. Therefore
I would like to have one option per attribute which I can express perfectly
fine in HTL only (without being forced to rely on some backing Java model).
> ResourceRuntimeExtension: Allow to pass arbitrary options a request
> attributes via data-sly-resource
> ----------------------------------------------------------------------------------------------------
>
> Key: SLING-7515
> URL: https://issues.apache.org/jira/browse/SLING-7515
> Project: Sling
> Issue Type: Improvement
> Components: Scripting
> Affects Versions: Scripting HTL Engine 1.0.48-1.3.1
> Reporter: Konrad Windszus
> Priority: Major
>
> Currently it is only possible to pass parameters to another script/servlet
> when using {{data-sly-resource}} with the options to modify the selector
> (https://github.com/apache/sling-org-apache-sling-scripting-sightly/blob/master/src/main/java/org/apache/sling/scripting/sightly/impl/engine/extension/ResourceRuntimeExtension.java).
> It would be good if either all unknown options or only those with a specific
> prefix would be passed as request attributes to the other script/servlet.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
