You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2013/10/17 17:35:41 UTC

[jira] [Updated] (SLING-3038) Take "context" service property into account when using BindingsValuesProvider

     [ https://issues.apache.org/jira/browse/SLING-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bertrand Delacretaz updated SLING-3038:
---------------------------------------

    Fix Version/s: Scripting Core 2.0.26

> Take "context" service property into account when using BindingsValuesProvider
> ------------------------------------------------------------------------------
>
>                 Key: SLING-3038
>                 URL: https://issues.apache.org/jira/browse/SLING-3038
>             Project: Sling
>          Issue Type: Bug
>          Components: Health Check
>    Affects Versions: Scripting Core 2.0.24
>            Reporter: Bertrand Delacretaz
>            Assignee: Bertrand Delacretaz
>            Priority: Minor
>             Fix For: Scripting Core 2.0.26
>
>         Attachments: SLING-3038.patch
>
>
> As discussed at http://sling.markmail.org/thread/dzdgfx3n6i5ftkjw , being able to restrict BindingsValuesProvider (BVP) services to specific contexts (request processing, health checks, workflow etc) would be useful.
> The first step is to modify the scripting setup in DefaultSlingScript so that any BVP which has a "context" service property which doesn't include a "request" value is ignored.
> Other components which use BVPs can then select then based on the value of their "context" service property.



--
This message was sent by Atlassian JIRA
(v6.1#6144)