WebDAV and executed scripts

Hi all, With the new resource tree mechanism built in last week, it now becomes possible to directly address scripts (and servlets) and have them executed on the server. This has its advantages in certain aspects, such as not requiring a sentinel repository node to be able to implement administrat

[jira] Resolved: (SLING-205) launcher/app and launchpad/launchpad-webapp delete 'sling' directory when invoking from sling-builder

[ https://issues.apache.org/jira/browse/SLING-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-205. Resolution: Fixed > launcher/app and launchpad/launchpad-webapp delete 'sling' directory whe

[jira] Updated: (SLING-205) launcher/app and launchpad/launchpad-webapp delete 'sling' directory when invoking from sling-builder

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

[jira] Commented: (SLING-193) Rhino debugger for server-side javascript

[ https://issues.apache.org/jira/browse/SLING-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12563063#action_12563063 ] Bertrand Delacretaz commented on SLING-193: --- I agree that having a server-side GUI

[jira] Commented: (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:comment-tabpanel&focusedCommentId=12563035#action_12563035 ] Tobias Bocanegra commented on SLING-206: it seems that the bindResourceProvider() is

[jira] Commented: (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:comment-tabpanel&focusedCommentId=12563034#action_12563034 ] Tobias Bocanegra commented on SLING-206: debugging shows, that the 'componentContext

[jira] Commented: (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:comment-tabpanel&focusedCommentId=12563033#action_12563033 ] Tobias Bocanegra commented on SLING-206: i'm getting this all over the log file: 2

[jira] Updated: (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 ] Tobias Bocanegra updated SLING-206: --- Attachment: config_status.txt configuration status dump of sling cosole > servlet not picked

Re: servlet registration

https://issues.apache.org/jira/browse/SLING-206 regards, toby On 1/28/08, Felix Meschberger <[EMAIL PROTECTED]> wrote: > Hi Toby, > > This is strange and I would qualify this a bug. Could you please file an > issue in JIRA attaching the output of the "Configuration > Status" ( /sling/status ) pag

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

servlet not picked up by resolver unless i restart my bundle Key: SLING-206 URL: https://issues.apache.org/jira/browse/SLING-206 Project: Sling Issue Type: Bug Components

Re: servlet registration

Hi Toby, This is strange and I would qualify this a bug. Could you please file an issue in JIRA attaching the output of the "Configuration Status" ( /sling/status ) page to it ? The main question is, whether the ServletResolver bundle is launched before or after the bundle containing your servlet

Re: direct execution of scripts

Am Sonntag, den 27.01.2008, 00:53 +0100 schrieb Tobias Bocanegra: > hi, > i remember a discussion about allowing direct script execution (a > request to /foo/my.jsp executes the script instead of delivering the > content). > > while this might by funny (and sometimes useful) Well, it is not funn

Re: svn commit: r615221 - /incubator/sling/trunk/launcher/app/pom.xml

see my issue regarding this problem: https://issues.apache.org/jira/browse/SLING-205 i think instrumenting cargo to use a sling.home inside the taget directory resolves this problem. regads, toby On 1/27/08, Felix Meschberger <[EMAIL PROTECTED]> wrote: > Hi, > > Should we really delete stuff outs

Re: svn commit: r615221 - /incubator/sling/trunk/launcher/app/pom.xml

Hi, Should we really delete stuff outside the target folder upon clean ? Usually I run the launcher with the sling.home outside of target exactly for not having it removed upon each "maven clean". Regards Felix Am Freitag, den 25.01.2008, 13:44 + schrieb [EMAIL PROTECTED]: > Author: bdelac

[jira] Commented: (SLING-193) Rhino debugger for server-side javascript

[ https://issues.apache.org/jira/browse/SLING-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12563027#action_12563027 ] Felix Meschberger commented on SLING-193: - While it certainly is a nice addition, I