[
https://issues.apache.org/jira/browse/SLING-8867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu resolved SLING-8867.
---------------------------------
Resolution: Fixed
Implemented in [commit
fd25b3e|https://github.com/apache/sling-org-apache-sling-scripting-jsp/commit/fd25b3e].
> Enhance the pageContext with the values provided by the SlingBindings
> ---------------------------------------------------------------------
>
> Key: SLING-8867
> URL: https://issues.apache.org/jira/browse/SLING-8867
> Project: Sling
> Issue Type: Improvement
> Components: Scripting
> Reporter: Radu Cotescu
> Assignee: Radu Cotescu
> Priority: Major
> Fix For: Scripting JSP 2.4.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> SLING-8737 brought support for using lazily evaluated bindings. The JSP
> script engine, however, although sets the {{SlingBindings}} as a request
> attribute, does not do anything else to facilitate the access to the
> bindings' values. Instead, this is delegated partially to the
> {{<sling:defineObjects/>}} tag. However, this tag has the potential of
> expanding all values which are provided lazily, irrespective of what values
> the JSP script being evaluated needs.
> While modifying the {{<sling:defineObjects/>}} tag is out of the question,
> for backwards-compatibility reasons, the JSP engine could make the values
> provided by the {{SlingBindings}} available in the {{pageContext}}, if the
> context hasn't already defined identical attributes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
