[
https://issues.apache.org/jira/browse/SLING-3217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13808813#comment-13808813
]
Felix Meschberger commented on SLING-3217:
------------------------------------------
While I agree that this helps EL and probably makes sense in that context, I am
afraid of the discrepancy we generate with respect to what is known to EL and
what is known to scriptlets.
And yes, your are most probably right, it would be cool if we could expose all
SlingBindings to the JSPs -- but we are also probably lacking the appropriate
type information to make this happen.
> Automatically expose SlingBindings object through EL
> ----------------------------------------------------
>
> Key: SLING-3217
> URL: https://issues.apache.org/jira/browse/SLING-3217
> Project: Sling
> Issue Type: Improvement
> Components: Scripting
> Reporter: Justin Edelson
> Attachments: SLING-3217.patch
>
>
> JSP scripts need to use the <sling:defineObjects/> (or a subclass) in order
> to expose the Sling Bindings objects (i.e. `resource`) for use in a JSP page.
> This shouldn't be necessary if we provide a custom ELResolver.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
