[
https://issues.apache.org/jira/browse/SLING-3217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Edelson updated SLING-3217:
----------------------------------
Attachment: SLING-3217.patch
With this patch, custom ELResolvers can be provided through OSGi services
(because that's the Sling way!)
With this patch, you still need <sling:defineObjects/> to use Sling Bindings
objects in scriptlets, but not in EL expressions, so
${resource.path}
works without <sling:defineObjects/>
> 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)
