Hi, Adding more options to sling:include makes perfect sense, but changing the behavior of sling:call does not. When I write
<sling:call script="foo.jsp"/> I mean "call the script foo.jsp". I don't mean "call any script named foo." Regards, Justin On Fri, Aug 22, 2014 at 6:51 AM, Julian Sedding <[email protected]> wrote: > Yes, I would be in favour of deprecating <sling:call/>. It never felt > very "slingish". If we can also get rid of <sling:eval/>, I believe we > could even simplify the ServletResolver and remove the methods that > were presumably added to support these tags. > > One option could be to extend the <sling:call/> tag in the following fashion: > * deprecate "script" attribute > * if the "script" attribute is present, remove the extension (i.e. > last dot) and interpret as selectorString > * add new attribute "selectors", which is implemented like the > proposed <sling:partial/> tag > > Unless I am missing something, this would provide backwards > compatibility, while at the same time supporting Gabriel's use-case. > > Regards > Julian
