[
https://issues.apache.org/jira/browse/SLING-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12984521#action_12984521
]
Justin Edelson commented on SLING-1941:
---------------------------------------
fixed in r1061592 and r1061593. protected keys are now only: request, response,
reader, sling, resource, out, and log
> BindingsValuesProvider implementations can't overwrite non-core properties
> during inclusion
> -------------------------------------------------------------------------------------------
>
> Key: SLING-1941
> URL: https://issues.apache.org/jira/browse/SLING-1941
> Project: Sling
> Issue Type: Bug
> Components: Scripting
> Reporter: Justin Edelson
> Assignee: Justin Edelson
> Fix For: Scripting Core 2.0.16
>
>
> As discussed in this email thread:
> http://sling.markmail.org/thread/m2bx2oabtylk2ykj, BindingsValuesProvider
> implementations get IllegalArgumentExceptions if they attempt to put a value
> into the bindings if the key is already used when one script includes another
> even if the key isn't a standard Sling bindings key.
> The bug is that the "protection" feature of BindingsValuesProvider support is
> too aggressive. It protects everything already in the bindings, but the
> original intent was to have only the standard Sling keys be protected.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
