You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2007/11/22 16:57:43 UTC
[jira] Resolved: (SLING-104) sling.include() provides a infinite
loop
[ https://issues.apache.org/jira/browse/SLING-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bertrand Delacretaz resolved SLING-104.
---------------------------------------
Resolution: Fixed
Fixed in revision 597442, request path info was not computed correctly for included requests.
Solved using the SlingRequestPaths class, see
http://svn.apache.org/repos/asf/incubator/sling/trunk/api/src/main/java/org/apache/sling/api/wrappers/SlingRequestPaths.java
> sling.include() provides a infinite loop
> ----------------------------------------
>
> Key: SLING-104
> URL: https://issues.apache.org/jira/browse/SLING-104
> Project: Sling
> Issue Type: Bug
> Components: microsling
> Reporter: Christophe Lombart
> Assignee: Bertrand Delacretaz
>
> I have created a new esp template for the nt:unstructured type which contains the following code :
> <%= sling.include("/content/testing/1194989095463.html") %>
> If I'm retrieving a resource based on this type (eg. : /content/testing.html), I get an infinitive loop. It seems that Microsling tries to retrieve always the same content (/content/testing.html).
> I have the same behavior with other paths and with velocity templates.
> Here is the log :
> 13.11.2007 22:42:43 *INFO * MicroslingResourceResolver: Path '/content/testing.html' does not resolve to an Item (MicroslingResourceResolver.java, line 274)
> 13.11.2007 22:42:43 *INFO * MicroslingResourceResolver: Found Resource at path '/content/testing' (MicroslingResourceResolver.java, line 270)
> 13.11.2007 22:42:43 *DEBUG* MicroslingServletResolver: No Servlet found for resource type nt:unstructured (MicroslingServletResolver.java, line 127)
> 13.11.2007 22:42:43 *DEBUG* MicroslingScriptResolver: Looking for script with filename=html.* under /sling/scripts/nt/unstructured (MicroslingScriptResolver.java, line 194)
> 13.11.2007 22:42:43 *INFO * MicroslingScriptResolver: Found nt:file script node /sling/scripts/nt/unstructured/html.esp for Resource=JcrNodeResource, type=nt:unstructured, path=/content/testing (MicroslingScriptResolver.java, line 228)
> 13.11.2007 22:45:02 *INFO * MicroslingResourceResolver: Path '/content/testing.html' does not resolve to an Item (MicroslingResourceResolver.java, line 274)
> 13.11.2007 22:45:02 *INFO * MicroslingResourceResolver: Found Resource at path '/content/testing' (MicroslingResourceResolver.java, line 270)
> 13.11.2007 22:45:02 *DEBUG* MicroslingServletResolver: No Servlet found for resource type nt:unstructured (MicroslingServletResolver.java, line 127)
> 13.11.2007 22:45:02 *DEBUG* MicroslingScriptResolver: Looking for script with filename=html.* under /sling/scripts/nt/unstructured (MicroslingScriptResolver.java, line 194)
> 13.11.2007 22:45:02 *INFO * MicroslingScriptResolver: Found nt:file script node /sling/scripts/nt/unstructured/html.esp for Resource=JcrNodeResource, type=nt:unstructured, path=/content/testing (MicroslingScriptResolver.java, line 228)
> 13.11.2007 22:45:56 *INFO * MicroslingResourceResolver: Path '/content/testing.html' does not resolve to an Item (MicroslingResourceResolver.java, line 274)
> 13.11.2007 22:45:56 *INFO * MicroslingResourceResolver: Found Resource at path '/content/testing' (MicroslingResourceResolver.java, line 270)
> 13.11.2007 22:45:56 *DEBUG* MicroslingServletResolver: No Servlet found for resource type nt:unstructured (MicroslingServletResolver.java, line 127)
> 13.11.2007 22:45:56 *DEBUG* MicroslingScriptResolver: Looking for script with filename=html.* under /sling/scripts/nt/unstructured (MicroslingScriptResolver.java, line 194)
> 13.11.2007 22:45:56 *INFO * MicroslingScriptResolver: Found nt:file script node /sling/scripts/nt/unstructured/html.esp for Resource=JcrNodeResource, type=nt:unstructured, path=/content/testing (MicroslingScriptResolver.java, line 228)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.