Sorry, I incorrectly copied down the script names for (3) and (4) they are:
(3) /apps/test/B/edit.small.html.jsp
(4) /apps/test/B/view.small.html.jsp
However, your suggestion works ((A) /apps/test/B/edit/small.html.jsp).
It's a little confusing to me though, since (B)
/apps/test/B/edit/small/html.jsp also works.
Does that imply that at only the first dot-separated component of the
scriptname can be considered as part of the selector string? Wouldn't
it be more consistent to either:
a) consider all dot-separated components part of the selector except the
last 2 (those last 2 being the extension and the script language
identifier) (like (3) and (4) or
b) only allow the script name to be <extension>.<script language
identifier>, and selectors have to be /-separated components of the path
(like (B) above)
Is there a specific reason for the current implementation behavior?
Regards,
Rory
Felix Meschberger wrote:
Hi Rory,
Rory Douglas schrieb:
I have a resource of type test/A, which has 2 rendering scripts at:
(1) /apps/test/A/edit.html.jsp and
(2) /apps/test/A/view.html.jsp.
In those scripts I render resources of type test/B, which has rendering
scripts at:
(3) /apps/test/B/edit.small.jsp and
(4) /apps/test/B/view.small.jsp
Shouldn't these rather be
(3) /apps/test/B/edit/small.html.jsp and
(4) /apps/test/B/view/small.html.jsp
?
Regards
Felix
(5) /apps/test/B/edit.html.jsp
What is the correct syntax of a <sling:include tag> to include the
edit.small rendering (3) of test/B inside the edit rendering (1) of test/A?
I have <sling:include replaceSelectors="edit.small" path="..." /> but
that doesn't work. I also tried addSelectors="small" but that didn't
work either. Both of those yield an include of edit.html.jsp (5)
instead of edit.small.html.jsp (3).
Rory
