[jira] Created: (SLING-104) sling.include() provides a infinite loop
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
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.
[jira] Closed: (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
]
Christophe Lombart closed SLING-104.
Tested and it works. Thanks
> 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.
[jira] Created: (SLING-990) Prototype for a Sling Explorer implementation based on GWT
Prototype for a Sling Explorer implementation based on GWT -- Key: SLING-990 URL: https://issues.apache.org/jira/browse/SLING-990 Project: Sling Issue Type: New Feature Components: Extensions Reporter: Christophe Lombart Following the Sling Explorer proposal [1], I have started an implementation with the SwartGwt UI framework [2] (based on GWT and under LGPL licence). Not sure but I think that LGPL is compatible with the Apache project. Until now, it is just a prototype. Can you review the code and see if this Gwt application is well integrated with Sling ? [1] http://cwiki.apache.org/SLING/sling-based-jcr-explorer.html [2] http://code.google.com/p/smartgwt/ -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-990) Prototype for a Sling Explorer implementation based on GWT
[ https://issues.apache.org/jira/browse/SLING-990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christophe Lombart updated SLING-990: - Attachment: Sling Explorer.zip Here is the code. The README file contains information on useful maven command & GWT setting. > Prototype for a Sling Explorer implementation based on GWT > -- > > Key: SLING-990 > URL: https://issues.apache.org/jira/browse/SLING-990 > Project: Sling > Issue Type: New Feature > Components: Extensions >Reporter: Christophe Lombart > Attachments: Sling Explorer.zip > > > Following the Sling Explorer proposal [1], I have started an implementation > with the SwartGwt UI framework [2] (based on GWT and under LGPL licence). > Not sure but I think that LGPL is compatible with the Apache project. > Until now, it is just a prototype. Can you review the code and see if this > Gwt application is well integrated with Sling ? > [1] http://cwiki.apache.org/SLING/sling-based-jcr-explorer.html > [2] http://code.google.com/p/smartgwt/ -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-990) Prototype for a Sling Explorer implementation based on GWT
[ https://issues.apache.org/jira/browse/SLING-990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715866#action_12715866 ] Christophe Lombart commented on SLING-990: -- I will modify the JSON scripts. Ok for LICENSE, NOTICE & DISCLAIMER. I will add them if we can resolve the license issue. The resources (images, css & js) are under LGPL. I took those files from Smart GWT 1.1 distribution. Maybe we can use others. If LGPL is an issue, we cannot continue to use SmartGwt because the current implementention requires 2 SmartGWT jars (see the pom.xml). Those jars are also under LGPL. There are used to run the application in the hosted mode and compile de java code into js. > Prototype for a Sling Explorer implementation based on GWT > -- > > Key: SLING-990 > URL: https://issues.apache.org/jira/browse/SLING-990 > Project: Sling > Issue Type: New Feature > Components: Extensions >Reporter: Christophe Lombart > Attachments: Sling Explorer.zip > > > Following the Sling Explorer proposal [1], I have started an implementation > with the SwartGwt UI framework [2] (based on GWT and under LGPL licence). > Not sure but I think that LGPL is compatible with the Apache project. > Until now, it is just a prototype. Can you review the code and see if this > Gwt application is well integrated with Sling ? > [1] http://cwiki.apache.org/SLING/sling-based-jcr-explorer.html > [2] http://code.google.com/p/smartgwt/ -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-990) Prototype for a Sling Explorer implementation based on GWT
[ https://issues.apache.org/jira/browse/SLING-990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12717683#action_12717683 ] Christophe Lombart commented on SLING-990: -- SmartGwt provides more advanced widgets. That's the main reason why I started the explorer with it. We can use GWT but it will take more time to provide a nice UI. SmartGWT is already based on a dual license (LGPL & commercial). I can refactor the project to use only GWT > Prototype for a Sling Explorer implementation based on GWT > -- > > Key: SLING-990 > URL: https://issues.apache.org/jira/browse/SLING-990 > Project: Sling > Issue Type: New Feature > Components: Extensions >Reporter: Christophe Lombart > Attachments: Sling Explorer.zip > > > Following the Sling Explorer proposal [1], I have started an implementation > with the SwartGwt UI framework [2] (based on GWT and under LGPL licence). > Not sure but I think that LGPL is compatible with the Apache project. > Until now, it is just a prototype. Can you review the code and see if this > Gwt application is well integrated with Sling ? > [1] http://cwiki.apache.org/SLING/sling-based-jcr-explorer.html > [2] http://code.google.com/p/smartgwt/ -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-990) Prototype for a Sling Explorer implementation based on GWT
[ https://issues.apache.org/jira/browse/SLING-990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12717703#action_12717703 ] Christophe Lombart commented on SLING-990: -- Thanks for your comments. Yes, it is just a prototype and it is read-only :-) I would like to get more comments before adding more features. What's the conclusion for SmartGwt ? I can make a try with SmartGwt folks to see if it is not possible to change their license. Or maybe you ? because you have more ASF/open source experience. Your arguments will be certainly better :-) > Prototype for a Sling Explorer implementation based on GWT > -- > > Key: SLING-990 > URL: https://issues.apache.org/jira/browse/SLING-990 > Project: Sling > Issue Type: New Feature > Components: Extensions >Reporter: Christophe Lombart > Attachments: Sling Explorer.zip > > > Following the Sling Explorer proposal [1], I have started an implementation > with the SwartGwt UI framework [2] (based on GWT and under LGPL licence). > Not sure but I think that LGPL is compatible with the Apache project. > Until now, it is just a prototype. Can you review the code and see if this > Gwt application is well integrated with Sling ? > [1] http://cwiki.apache.org/SLING/sling-based-jcr-explorer.html > [2] http://code.google.com/p/smartgwt/ -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
