Re: WebDAV and executed scripts

On Jan 28, 2008 8:57 AM, Felix Meschberger [EMAIL PROTECTED] wrote: ...I propose to only execute directly addressed scripts if the request extension (RequestPathInfo.getExtension()) is not null. If the request extension is null, the directly addressed script is not executed Seems

Re: servlet registration

On Jan 28, 2008 12:13 AM, Felix Meschberger [EMAIL PROTECTED] wrote: ...The main question is, whether the ServletResolver bundle is launched before or after the bundle containing your servlet Could we make use of OSGi's run levels to better control this? Assuming bundles with a lower run

Board Report Feb/08

Hi all, Time is approaching to deliver our board report. I prepared the report page on our wiki [1] and invite you all to review and ammend where appropriate. Thanks and Regards Felix [1] http://cwiki.apache.org/confluence/x/4REB

[jira] Assigned: (SLING-206) servlet not picked up by resolver unless i restart my bundle

[ https://issues.apache.org/jira/browse/SLING-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger reassigned SLING-206: --- Assignee: Felix Meschberger servlet not picked up by resolver unless i restart my

Re: Board Report Feb/08

On Jan 28, 2008 9:15 AM, Felix Meschberger [EMAIL PROTECTED] wrote: ...Time is approaching to deliver our board report. I prepared the report page on our wiki [1] and invite you all to review and ammend where appropriate Thanks - added a point saying that we can expect a first release

Re: direct execution of scripts

Hi Bertrand, Am Montag, den 28.01.2008, 09:12 +0100 schrieb Bertrand Delacretaz: On Jan 28, 2008 12:00 AM, Felix Meschberger [EMAIL PROTECTED] wrote: Am Sonntag, den 27.01.2008, 00:53 +0100 schrieb Tobias Bocanegra: ... ps: if this is really needed, it could be done using a mixin node

[jira] Resolved: (SLING-204) add svn ignore pattern for intellij module file

[ https://issues.apache.org/jira/browse/SLING-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz resolved SLING-204. --- Resolution: Fixed Done using this: $ cat /tmp/ignore target sling bin logs

[jira] Assigned: (SLING-179) ResourceResolver should not go up the path for GET requests

[ https://issues.apache.org/jira/browse/SLING-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz reassigned SLING-179: - Assignee: Bertrand Delacretaz ResourceResolver should not go up the path for GET

[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: --- We could remove the need for locking by using the id as the node name and not allowing same name

Re: Board Report Feb/08

Hi Jukka, Am Montag, den 28.01.2008, 11:11 +0200 schrieb Jukka Zitting: The ASF board is asking all TLPs to review their use of cryptography and to check that the requirements of the export control policy [1] are met. Does Sling use cryptography somewhere? If not, it would be good to add a

[jira] Resolved: (SLING-208) Detect infinite loops in sling.include

[ https://issues.apache.org/jira/browse/SLING-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz resolved SLING-208. --- Resolution: Fixed Implemented in revision 615881, maximum recursion level for

[jira] Updated: (SLING-209) ResourceResource is not adaptable to OCM

[ https://issues.apache.org/jira/browse/SLING-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-209: --- Assignee: Carsten Ziegeler Remaining Estimate: 0h Original Estimate: 0h

[jira] Commented: (SLING-207) Status code 500 not reported to client for infinite loop in sling.include

[ https://issues.apache.org/jira/browse/SLING-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12563156#action_12563156 ] Bertrand Delacretaz commented on SLING-207: --- To clarify, the status 500 is caused

SLING-207: HTTP status code for included requests

Hi, See SLING-207, in an ESP script like this one: body % sling.include(resource.getPath() + .html); % /body The include rightly causes a server error due to the (just added) SLING-208 infinite loop detection. However, client receives a status 200 OK in this case. Do we want

[jira] Created: (SLING-207) Status code 500 not reported to client for infinite loop in sling.include

Status code 500 not reported to client for infinite loop in sling.include - Key: SLING-207 URL: https://issues.apache.org/jira/browse/SLING-207 Project: Sling Issue

Re: WebDAV - committed before 401 Unauthorized (was: A quick build question)

Ahaaa! In your previous psot, you misspelled the url :) You said it was different, and only /dav, but now I saw that you write /dev/default in this post. And that worked (releived). Back to work PS On Jan 25, 2008 5:59 PM, Bertrand Delacretaz [EMAIL PROTECTED] wrote: Hi Peter, On Jan 25,

[jira] Closed: (SLING-204) add svn ignore pattern for intellij module file

[ https://issues.apache.org/jira/browse/SLING-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tobias Bocanegra closed SLING-204. -- great. thanks. add svn ignore pattern for intellij module file

[jira] Created: (SLING-209) ResourceResource is not adaptable to OCM

ResourceResource is not adaptable to OCM Key: SLING-209 URL: https://issues.apache.org/jira/browse/SLING-209 Project: Sling Issue Type: Bug Components: ServletResolver Reporter:

Re: SLING-207: HTTP status code for included requests

Hi, Am Dienstag, den 29.01.2008, 08:41 +0100 schrieb Bertrand Delacretaz: On Jan 29, 2008 8:28 AM, Felix Meschberger [EMAIL PROTECTED] wrote: ...If the response has already been committed at the time the infinte loop detection aborts processing, it is not possible to send 500 any more

Re: SLING-207: HTTP status code for included requests

Hi, I agree, that returning 500 might be desirable, but If the response has already been committed at the time the infinte loop detection aborts processing, it is not possible to send 500 any more. There is also a difference in request inclusion between Sling and the Servlet API: In the