[
https://issues.apache.org/jira/browse/SLING-8126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Peltier reopened SLING-8126:
------------------------------------
> add pipes as binding provider for a given pipe
> ----------------------------------------------
>
> Key: SLING-8126
> URL: https://issues.apache.org/jira/browse/SLING-8126
> Project: Sling
> Issue Type: Improvement
> Components: pipes
> Affects Versions: Pipes 3.0.2
> Reporter: Nicolas Peltier
> Assignee: Nicolas Peltier
> Priority: Major
> Fix For: Pipes 3.1.0
>
>
> additional bindings are for now too rigid:
> - you can only add them at the root pipe level
> - their value is an expression, which is cool but often not practical: you
> might need a specific resource in the current execution context. ideal would
> be to add a pipe as a provider to fetch it.
> Proposal is:
> # allow additionalBindings & additionalScripts nodes in all pipes & subpipes
> of a pipe declaration, like global & local scope variables,
> # allow additionalBindings/providers subnode, that will be a set of pipe to
> execute in parallel in the current context (sharing pipe's binding), taking
> the first resource returned as binding value, the pipe name as binding name
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
