I would be in favour of having just one tag, the include one - so if I see it correctly the only problem is that it changes the set of visible selectors. So if we allow a way to deal with that with the include tag, we have a single tag and people have not to wonder which tag to use when.
Carsten 2014-08-22 12:51 GMT+02:00 Julian Sedding <jsedd...@gmail.com>: > 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 > -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
