Wow, couldn't believe this was working, very nice!! :) Thanks!
On 22/08/14 11:17, "Carsten Ziegeler" <[email protected]> wrote: >You can simply use sling:include instead, add a selector and your script >act on that specific selector - that's language independent. > >Carsten > > >2014-08-22 10:50 GMT+02:00 Gabriel Walt <[email protected]>: > >> >> Thanks for your answers! Let me try to provide more context and be more >> specific. >> >> With sling:resourceSuperType (or with /apps /libs overlaying), you can >> customize any script of your component. A common practice is to split >> large script templates into partials that can then each be independently >> customized, to avoid full script duplication, and to adapt only parts >> of it. >> >> The typical example is a page component that can for instance end up >>with >> a structure like: >> - page.jsp >> - head.jsp >> - headlibs.jsp >> - body.jsp >> - top.jsp >> - content.jsp >> - bottom.jsp >> - bodylibs.jsp >> >> These scripts are usually all included with something like a sling:call, >> but then this makes it impossible in an extending component to use a >> different script language than the one used in the super-type (so in our >> example we'd be forced to go with JSP, and couldn't use ESP, Sightly, >>etc). >> >> Thus, it would be nice to be able to do an include of script partials >>that >> are not binding to a particular script language, like for instance: >> <sling:call script="myscript.*" /> >> instead of: >> <sling:call script="myscript.jsp" /> >> >> Best, >> Gabriel >> >> >> > > >-- >Carsten Ziegeler >Adobe Research Switzerland >[email protected]
