[
https://issues.apache.org/jira/browse/SLING-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz updated SLING-3038:
---------------------------------------
Attachment: SLING-3038.patch
SLING-3038.patch should work but if I use the latest script.api snapshot in the
launchpad, two integration tests fail (JSONGroovyBuilderTest,
ScriptBindingsValuesProviderTest), apparently because the .groovy script engine
is disabled. Looks like the issue is not caused by my code, I'll investigate
further.
> 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: Scripting
> Affects Versions: Scripting Core 2.0.24
> Reporter: Bertrand Delacretaz
> Assignee: Bertrand Delacretaz
> Priority: Minor
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
