[jira] [Commented] (SLING-1500) Patch Submission: Expression Language (EL) Functions for JSP Taglib

["Felix Meschberger (JIRA)" <ji...@apache.org>]

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

Felix Meschberger commented on SLING-1500:
------------------------------------------

Thanks. I am +1 in general.

I wonder whether we should create a separate tag lib for the Resource API related tags and EL functions ?
                
> Patch Submission: Expression Language (EL) Functions for JSP Taglib
> -------------------------------------------------------------------
>
>                 Key: SLING-1500
>                 URL: https://issues.apache.org/jira/browse/SLING-1500
>             Project: Sling
>          Issue Type: Improvement
>          Components: Scripting
>    Affects Versions: Scripting JSP-Taglib 2.0.6
>            Reporter: Mark Adamcin
>            Priority: Minor
>              Labels: el, function, jsp, scripting, sling, taglib
>         Attachments: add-files.zip, SLING-1500.diff, taglib11.tld.patch
>
>
> I've noticed that the Sling Resource API is not very accessible for tag- and EL-focused JSP development. In order to promote readable JSP code, I created a set of static methods to implement commonly-used ResourceResolver methods as well as to expose the rather useful ResourceUtil methods as EL functions. The functions use ResourceWrappers to work around the isse https://issues.apache.org/jira/browse/SLING-1414 where the Resource.getPath() method is inaccessible in EL for JcrNodeResource objects.
> I've found these taglib functions to be very useful for Day CQ5 development, so I thought I'd offer to contribute them to the project.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira