Hi Ulrich
Looking at the Recent Requests trace you provided, I would suspect
that your topnav.jsp has an include on itself. This results in endless
recursion, which is evident by the error you get. I would expect the
error message to be a RecursionTooDeepException, indicating that the
nesting of
Sling follows the principal of clear separation between public APIs
and implementation. The ResourceResolver is an interface, used to
define the API contract. This provides Sling itself with the freedom
to change or move the implementation (which is ResourceResolverImpl
btw). The implementation
Right now I'm dealing with this problem: The node:
/apps/mywebsite/components/content/body.jsp references another jsp located at
/apps/mywebsite/components/topnav/topnav.jsp by the expression:
cq:include path = topnav resourceType = mywebsite/components/topnav /
within body.jsp.
When rendering
Hi Ulrich
I fear the Sling community cannot help you with the cq:include tag which is
part of the commercial CQ product.
Have you tried using the sling:include tag ?
Regards
Felix
Am 04.02.2013 um 07:50 schrieb Ulrich Schmidt:
Right now I'm dealing with this problem: The node:
That comes out with the same result or better with the same error.
But as you mention it: Isn't it Sling anyway resolving those resources. I asked
in my last thread for the ResourceResolver. This is just an interface. Is there
a CQ-implementation of this interface which resolves cq:include and a
