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 2017/12/12 13:58:00 UTC

[jira] [Commented] (SLING-7250) allow non persisted configurations for pipe

    [ https://issues.apache.org/jira/browse/SLING-7250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16287629#comment-16287629 ] 

Nicolas Peltier commented on SLING-7250:
----------------------------------------

removing this from pipes 2.0
this should be associated with decoupling of logic and state management (with something like boundable osgi components handling execution, and one class holding state passed as a parameter). This would be another version bump probably, but deserves bigger interest from community.

> allow non persisted configurations for pipe
> -------------------------------------------
>
>                 Key: SLING-7250
>                 URL: https://issues.apache.org/jira/browse/SLING-7250
>             Project: Sling
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: pipes 1.1.0
>            Reporter: Nicolas Peltier
>            Assignee: Nicolas Peltier
>
> for some usage of the pipe builder, it might be useful not to persist pipes before executing them



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)