Re SLING-221 and SLING-222

Hi, In Rev. 618697 [0]the following main chaines are introduced: (1) Replace SlingScriptHelper.include(String path, RequestDispatcherOptions options) signature by SlingScriptHelper.include(String path, String options). (2) The implementation of the include method uses a request attribute to

Re: Re SLING-221 and SLING-222

Hi Felix, On Feb 6, 2008 9:04 AM, Felix Meschberger [EMAIL PROTECTED] wrote: ..SlingScriptHelper.include(String path, String options) ...(1) I do not understand the reason to change the method signature... The SlingScriptHelper is available in scripts as the sling variable, so to call

[Sling API] ResourceWrapper and SyntheticResource

Hi all, I would like to propose to create a ResourceWrapper class in the Sling API, which is just a simple wrapper around a delegatee resource analogous to what we have for servlet requests and responses. This simplifies the creation of pseudo-resources, for example to create resource based on

Re: [Sling API] ResourceWrapper and SyntheticResource

I would like to propose to create a ResourceWrapper class in the Sling API, which is just a simple wrapper around a delegatee resource analogous to what we have for servlet requests and responses. This simplifies the creation of pseudo-resources, for example to create resource based on

Re: [Sling API] ResourceWrapper and SyntheticResource

On Feb 6, 2008 9:26 AM, Felix Meschberger [EMAIL PROTECTED] wrote: ...I would like to propose to create a ResourceWrapper class in the Sling API, which is just a simple wrapper around a delegatee resource analogous to what we have for servlet requests and responses +1 Second, I propose

Re: Re SLING-221 and SLING-222

..SlingScriptHelper.include(String path, String options) ...(1) I do not understand the reason to change the method signature... The SlingScriptHelper is available in scripts as the sling variable, so to call sling.include with options the natural way in scripts is to do

Re: [Sling API] ResourceWrapper and SyntheticResource

Am Mittwoch, den 06.02.2008, 09:54 +0100 schrieb Tobias Bocanegra: I would like to propose to create a ResourceWrapper class in the Sling API, which is just a simple wrapper around a delegatee resource analogous to what we have for servlet requests and responses. This simplifies the

[jira] Created: (SLING-225) Add SlingHttpServletRequest.getRequestDispatcher(String path, RequestDispatcherOptions options) method

Add SlingHttpServletRequest.getRequestDispatcher(String path, RequestDispatcherOptions options) method -- Key: SLING-225 URL:

[jira] Closed: (SLING-167) Default JSON rendering with selectable depth

[ https://issues.apache.org/jira/browse/SLING-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz closed SLING-167. - Resolution: Fixed 'infinity' recursion level implemented in revision 618936 Note that

[jira] Created: (SLING-226) Fix Resource resolution from request path

Fix Resource resolution from request path -- Key: SLING-226 URL: https://issues.apache.org/jira/browse/SLING-226 Project: Sling Issue Type: Bug Components: Resource Reporter:

[jira] Closed: (SLING-225) Add SlingHttpServletRequest.getRequestDispatcher(String path, RequestDispatcherOptions options) method

[ https://issues.apache.org/jira/browse/SLING-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed SLING-225. --- Resolution: Fixed Implemented new getter method in Rev. 618938. Add

Re: [Sling API] ResourceWrapper and SyntheticResource

I would like to propose to create a ResourceWrapper class in the Sling API, which is just a simple wrapper around a delegatee resource analogous to what we have for servlet requests and responses. This simplifies the creation of pseudo-resources, for example to create resource based

[jira] Commented: (SLING-226) Fix Resource resolution from request path

[ https://issues.apache.org/jira/browse/SLING-226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12566065#action_12566065 ] Tobias Bocanegra commented on SLING-226: i believe this is the correct solution.

[jira] Assigned: (SLING-222) using request.getRequestDispatcher() with an URL causes infinite loop

[ https://issues.apache.org/jira/browse/SLING-222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger reassigned SLING-222: --- Assignee: Felix Meschberger using request.getRequestDispatcher() with an URL causes

[jira] Issue Comment Edited: (SLING-221) sling:include should allow override of resource type

[ https://issues.apache.org/jira/browse/SLING-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12566077#action_12566077 ] fmeschbe edited comment on SLING-221 at 2/6/08 2:55 AM: -

[jira] Closed: (SLING-226) Fix Resource resolution from request path

[ https://issues.apache.org/jira/browse/SLING-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed SLING-226. --- Resolution: Fixed Implemented in Rev. 618949. Also updated the unit tests and javadoc to

[jira] Closed: (SLING-221) sling:include should allow override of resource type

[ https://issues.apache.org/jira/browse/SLING-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tobias Bocanegra closed SLING-221. -- thanks sling:include should allow override of resource type

[jira] Commented: (SLING-222) using request.getRequestDispatcher() with an URL causes infinite loop

[ https://issues.apache.org/jira/browse/SLING-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12566078#action_12566078 ] Felix Meschberger commented on SLING-222: - Modify last commit (Rev. 618697) slightly

[jira] Closed: (SLING-224) add .res extension to launchpad defaut servlet

[ https://issues.apache.org/jira/browse/SLING-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tobias Bocanegra closed SLING-224. -- great. thanks. add .res extension to launchpad defaut servlet

[jira] Commented: (SLING-222) using request.getRequestDispatcher() with an URL causes infinite loop

[ https://issues.apache.org/jira/browse/SLING-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12566127#action_12566127 ] Tobias Bocanegra commented on SLING-222: works for me :-) thanks. using

[jira] Created: (SLING-227) sling:include tag: use ResourceResolver.resolve(String) method to get the resource

sling:include tag: use ResourceResolver.resolve(String) method to get the resource -- Key: SLING-227 URL: https://issues.apache.org/jira/browse/SLING-227 Project: Sling

[jira] Closed: (SLING-227) sling:include tag: use ResourceResolver.resolve(String) method to get the resource

[ https://issues.apache.org/jira/browse/SLING-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed SLING-227. --- Resolution: Fixed Do not actually use the resolved resource just use it to test whether a

[jira] Closed: (SLING-222) using request.getRequestDispatcher() with an URL causes infinite loop

[ https://issues.apache.org/jira/browse/SLING-222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed SLING-222. --- Resolution: Fixed Fix Version/s: 2.0.0 Unit tests work and Toby has confirmed, that it

[jira] Commented: (SLING-227) sling:include tag: use ResourceResolver.resolve(String) method to get the resource

[ https://issues.apache.org/jira/browse/SLING-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12566162#action_12566162 ] Tobias Bocanegra commented on SLING-227: the latest fix produces endless loops when

[jira] Updated: (SLING-177) Improvements to event bundle

[ https://issues.apache.org/jira/browse/SLING-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-177: --- Assignee: Carsten Ziegeler Improvements to event bundle

Understanding and using the Sling stack

We're building a web content management system, and Sling looks like it provides a lot of the stuff we need. But we're having a hard time understanding the Sling technology stack, and where to inject our own functionality. Basically, what we need from Sling is a way of mapping URLs to JCR nodes,

[jira] Created: (SLING-229) uja post servlet should also respect some well known jcr property names for auto generation

uja post servlet should also respect some well known jcr property names for auto generation --- Key: SLING-229 URL: https://issues.apache.org/jira/browse/SLING-229

[jira] Updated: (SLING-229) uja post servlet should also respect some well known jcr property names for auto generation

[ https://issues.apache.org/jira/browse/SLING-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tobias Bocanegra updated SLING-229: --- Attachment: ujax_jcr_names-r619004.patch provides fix for this issue uja post servlet

Re: Understanding and using the Sling stack

Hi Vidar, On Feb 6, 2008 5:35 PM, Vidar Ramdal [EMAIL PROTECTED] wrote: ...what we need from Sling is a way of mapping URLs to JCR nodes, and different ways of rendering/styling the content Sling will definitely help you here, taking care of the URL to node mapping (called resolving the

RE: Understanding and using the Sling stack

I am in the same position as I have begun building out a store front / product catalog on top of sling. It is an ideal fit IMHO. Right now it is deployed as a bundle, but the plan is to have the ability to deploy in other containers (JBoss, Tomcat, Geronimo etc) I could use the same input as well

[jira] Commented: (SLING-227) sling:include tag: use ResourceResolver.resolve(String) method to get the resource

[ https://issues.apache.org/jira/browse/SLING-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12566414#action_12566414 ] Tobias Bocanegra commented on SLING-227: the problem is along this lines:

[jira] Issue Comment Edited: (SLING-227) sling:include tag: use ResourceResolver.resolve(String) method to get the resource

[ https://issues.apache.org/jira/browse/SLING-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12566414#action_12566414 ] tripod edited comment on SLING-227 at 2/6/08 4:34 PM: the

Re: Understanding and using the Sling stack

Thank you, your answer is very clarifying. On 2/6/08, Bertrand Delacretaz [EMAIL PROTECTED] wrote: ...Examples of how to build an application upon the Sling framework would be of great help to us We don't have any serious examples at the moment, this is definitely next on our list

Re: resource type inheritance

Hi all, I think this idea is certainly worth considering, though of course with a slightly more general approach: (1) Extend the Resource API to include a method String getSuperResourceType() - returns the resource super type or null if there is none (2) JCR Resource

[jira] Reopened: (SLING-227) sling:include tag: use ResourceResolver.resolve(String) method to get the resource

[ https://issues.apache.org/jira/browse/SLING-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger reopened SLING-227: - Thanks for looking into this. While this is not directly linked to the new resolution