You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2010/04/06 12:13:33 UTC

[jira] Resolved: (SLING-586) Respect resource type hierarchy in static @include directive.

     [ https://issues.apache.org/jira/browse/SLING-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved SLING-586.
------------------------------------

    Resolution: Won't Fix

As already explained in the mailing list (see referenced thread) introducing this include would create more problems than it solves.
Therefore I'm resolving this issue now as won't fix.
However I'll be working on a different solution as part of SLING-585

> Respect resource type hierarchy in static @include directive.
> -------------------------------------------------------------
>
>                 Key: SLING-586
>                 URL: https://issues.apache.org/jira/browse/SLING-586
>             Project: Sling
>          Issue Type: New Feature
>          Components: Scripting
>            Reporter: Tobias Bocanegra
>            Priority: Minor
>
> I'm looking for a way to include a jsp script from within another but
> respecting the resource type hierarchy. so for example:
> + myapp
>  + A
>       + A.jsp
>       + content.jsp
>  + B
>       - sling:resourceSuperType = "A"
>       + B.jsp
> and in my B.jsp i want to include the "content.jsp" but respecting the resource type hierarchy.
> suggest to extend the way how the jsp compiler resolves the path for included scripts, by respective the resource type hierarchy.
> see http://markmail.org/message/la4rvmcdd6whpvhl

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.