On 24.07.2014, at 19:11, Justin Edelson <jus...@justinedelson.com> wrote:
> If the author didn't want to > do that, they shouldn't use sling:call and instead use sling:include > with replaceSelectors. Right. sling:call addresses the script and that is simply wrong - it needs to be a sling:include and strictly rely on sling resource resolution (selectors, extensions etc.). If you use sling:call and address the script, you of course tie yourself to the script engine in question (i.e. usually JSP). Cheers, Alex
