[
https://issues.apache.org/jira/browse/SLING-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12618386#action_12618386
]
Felix Meschberger commented on SLING-567:
-----------------------------------------
Hmpf, sorry, I was completely mislead. You are right. So back to field 1 ;-)
As SlingScriptHelperinclude() is based on RequestDispatcher.include() this
behaviour is still expected. So the "workarounds" presented by Tobias are
probably the way to go.
Have you tried to use:
RequestDispatcher rd = request.getRequestDispatcher(....);
rd.include(request, response);
instead of SlingScriptHelper.include() ?
> 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
> 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.
