You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Justin Edelson (JIRA)" <ji...@apache.org> on 2014/06/04 23:55:01 UTC

[jira] [Commented] (SLING-3217) Automatically expose SlingBindings object through EL

    [ https://issues.apache.org/jira/browse/SLING-3217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14018251#comment-14018251 ] 

Justin Edelson commented on SLING-3217:
---------------------------------------

I forgot that this issue was never resolved. [~fmeschbe] would you care to revisit your comment? As I wrote above, I think the divergence between EL scope and scripting variables is acceptable (and, frankly) pre-existing.

> 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.2#6252)