You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Nicolas Peltier (JIRA)" <ji...@apache.org> on 2016/07/25 16:40:20 UTC
[jira] [Updated] (SLING-5818) make sling pipe writer a persistent
configuration
[ https://issues.apache.org/jira/browse/SLING-5818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nicolas Peltier updated SLING-5818:
-----------------------------------
Attachment: SLING-5818.patch
attaching patch that brings in "OutputWriter" interface,
- PlumberServlet systematically uses it for outputing pipe execution results, with default writer outputing size & paths,
- CustomWriter can be defined by adding a "writer" subnode to the resource, properties being dubbed in the output (with instantiation of the values),
- CustomJsonWriter is a variation of CustomWriter, that comes from a JSON Object passed as a request parameter
> make sling pipe writer a persistent configuration
> -------------------------------------------------
>
> Key: SLING-5818
> URL: https://issues.apache.org/jira/browse/SLING-5818
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Reporter: Nicolas Peltier
> Attachments: SLING-5818.patch
>
>
> right now, the only way to configure the output of a pipe is to add a json as parameter of the pipe request. Sometimes the output is as important/complex as the pipe itself, and should be persisted.
> This could be also the opportunity to rewrite how writer is managed in a far from ideal if/else block.
> servlet/plumber should *always* take a writer in account, and call it each time,
> default being path writer, writer should still be overridable through a request parameter
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)