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 11:47:33 UTC

[jira] Resolved: (SLING-567) sling.include inclides fragments in the wrong order

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

Carsten Ziegeler resolved SLING-567.
------------------------------------

    Resolution: Not A Problem

As discussed this is the expected behaviour, therefore I'm closing this issue now

> sling.include inclides fragments in the wrong order
> ---------------------------------------------------
>
>                 Key: SLING-567
>                 URL: https://issues.apache.org/jira/browse/SLING-567
>             Project: Sling
>          Issue Type: Bug
>          Components: Scripting
>    Affects Versions: Scripting JSP 2.0.2
>            Reporter: Michael Marth
>
> (This is observed in revision 670551)
> consider a jsp "/apps/myapp/a.jsp" which contains:
> aaa
> <% sling.include(currentNode.getPath() + ".b.html"); %>
> and another jsp "/apps/myapp/b.jsp" which contains
> bbb
> if i execute /content/myapp/mynode.a.html i get
> bbb
> aaa
> expected result is:
> aaa
> bbb

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