[
https://issues.apache.org/jira/browse/SLING-2353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13186296#comment-13186296
]
Jeff Young commented on SLING-2353:
-----------------------------------
<sling:include> with a null resource (whether specified as null or defaulted to
null) doesn't appear to have any value other than backwards compatibility.
It's certainly not an elegant way to include self, nor does it appear to be the
only way.
Being able to include self (with other selectors/extensions) certainly does
have value, but as stated, we don't need "include null" to accomplish that.
So, if we need backward compatibility, then I'd favour WONTFIX. Otherwise, I'd
favour throwing an IllegalArgumentException.
> Prevent <sling:include resource="<%= null %>" /> to include itself
> ------------------------------------------------------------------
>
> Key: SLING-2353
> URL: https://issues.apache.org/jira/browse/SLING-2353
> Project: Sling
> Issue Type: Bug
> Components: Scripting
> Affects Versions: Scripting JSP-Taglib 2.1.2
> Reporter: Tobias Bocanegra
> Assignee: Carsten Ziegeler
> Priority: Minor
> Fix For: Scripting JSP-Taglib 2.1.4
>
>
> If you add this sling:include to a JSP <sling:include resource="<%= null %>"
> />
> then it will cause the page to keep including itself recursively making the
> server slow. there is a recursion limitation though to prevent endless loops.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
