Re: [PROPOSAL]: Add Resource.listChildren() method

David Nuescheler wrote: Hi guys, I agree with Lars. on top of that I would like to mention the following things: (1) I feel like with a getChildren() method we slowly see parts of the Node interface sneak in through the back door. I think it is fairly public that I am not a big fan of the

Re: various questions regarding alternative scripting engines

hi carsten, Ok, we can still argue about the name though... :) I would call it just node as we already have resource i agree that node would be intuitive. there are really two issues why i personally would mildly favor currentNode. a) when working with jcr node is a very frequently used

Re: various questions regarding alternative scripting engines

On Feb 15, 2008 5:17 PM, David Nuescheler [EMAIL PROTECTED] wrote: hi guys, var node = resource.adaptTo(Packages.javax.jcr.Node) i personally think this sucks since it is going to be a cryptic part in the beginning of all my esp scripts... You don't need this in ESP scripts, as those

[jira] Commented: (SLING-245) After reinstalling sling core, server shutdown hangs

[ https://issues.apache.org/jira/browse/SLING-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12569521#action_12569521 ] Felix Meschberger commented on SLING-245: - OK. thanks. I will keep this issue open

Re: [jira] Commented: (SLING-249) Allow mapping nodes to internet domains

Hi Bertrand, This is in fact a viable solution - provided you have a an Apache server to put in front - it is just another target you will have to manage.. Regards Felix Am Freitag, den 15.02.2008, 14:24 -0800 schrieb Bertrand Delacretaz (JIRA): [

Re: help, my content model looks un-Slingable

Hi, On Feb 16, 2008 2:20 PM, Felix Meschberger [EMAIL PROTECTED] wrote: Am Freitag, den 15.02.2008, 18:36 +0200 schrieb Jukka Zitting: How about allowing a sling:config child node that could be added to any node and could contain script and servlet mappings and other configuration settings

Re: help, my content model looks un-Slingable

Hi, Am Samstag, den 16.02.2008, 14:26 +0200 schrieb Jukka Zitting: Hi, On Feb 16, 2008 2:20 PM, Felix Meschberger [EMAIL PROTECTED] wrote: Am Freitag, den 15.02.2008, 18:36 +0200 schrieb Jukka Zitting: How about allowing a sling:config child node that could be added to any node and

Re: help, my content model looks un-Slingable

Hi David, Am Samstag, den 16.02.2008, 09:43 +0100 schrieb David Nuescheler: Hi Jukka, I think that's a great idea. On top of that we used in microjax in case a node was not mapped we tried the following. if the node was located in /content/xyz we tried /apps/xyz as the default resource

[jira] Closed: (SLING-105) JCR logon should be configurable

[ https://issues.apache.org/jira/browse/SLING-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed SLING-105. --- Resolution: Won't Fix This need not be implemented any more as microsling is replaced by

[jira] Closed: (SLING-119) Provide an easy way to run microsling, requiring only a JVM

[ https://issues.apache.org/jira/browse/SLING-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed SLING-119. --- Resolution: Fixed Fix Version/s: 2.0.0 Assignee: Bertrand Delacretaz Closing

[jira] Closed: (SLING-129) microsling SyntheticResource, can be used for request paths which do not have matching repository Nodes

[ https://issues.apache.org/jira/browse/SLING-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed SLING-129. --- Resolution: Fixed Fix Version/s: 2.0.0 Assignee: Bertrand Delacretaz Closing

[jira] Commented: (SLING-114) Sling Javascript Client Templates (was: Ecmascript Client Templates)

[ https://issues.apache.org/jira/browse/SLING-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12569548#action_12569548 ] Felix Meschberger commented on SLING-114: - Can this be closed ? Sling Javascript

[jira] Closed: (SLING-83) Improve our Maven modules layout to make Sling easier to understand

[ https://issues.apache.org/jira/browse/SLING-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed SLING-83. -- Resolution: Fixed Fix Version/s: 2.0.0 Closing this issue as module reorganization is

[jira] Closed: (SLING-117) MicroslingResourceResolver should not go up the path hierarchy for GET requests

[ https://issues.apache.org/jira/browse/SLING-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed SLING-117. --- Resolution: Fixed Fix Version/s: 2.0.0 Assignee: Bertrand Delacretaz Fixed in

[jira] Closed: (SLING-159) JcrResourceResolverFactoryImpl fails if suffix contains illegal jcr character

[ https://issues.apache.org/jira/browse/SLING-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed SLING-159. --- Resolution: Fixed Fix Version/s: 2.0.0 Assignee: Felix Meschberger Closing

[jira] Closed: (SLING-2) Add support for declarative node type management

[ https://issues.apache.org/jira/browse/SLING-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed SLING-2. - Resolution: Invalid Closing this issue as invalid because object content mapping is not core to the

[jira] Closed: (SLING-59) Make microsling code very easy to read

[ https://issues.apache.org/jira/browse/SLING-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed SLING-59. -- Resolution: Fixed Fix Version/s: 2.0.0 Assignee: Bertrand Delacretaz This issue

MIME type support of Tika

Hi all, In SLING-135 Betrand Delacretaz hints at looking at Tika's MIME type support for Sling. Though we currently have a MIME type service in the commons/mime module, it is certainly worth investigating whether we should replace the implementation of this service by Tika's MIME type support.

[jira] Closed: (SLING-133) microsling Resource resolver and default renderers do not support Properties

[ https://issues.apache.org/jira/browse/SLING-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed SLING-133. --- Resolution: Fixed Fix Version/s: 2.0.0 Assignee: Bertrand Delacretaz This

[jira] Closed: (SLING-135) DefaultSlingServlet.spool is fragile w.r.t content-types

[ https://issues.apache.org/jira/browse/SLING-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed SLING-135. --- Resolution: Fixed Fix Version/s: 2.0.0 Assignee: Bertrand Delacretaz Closing

Re: help, my content model looks un-Slingable

Hi, Am Samstag, den 16.02.2008, 14:48 +0200 schrieb Jukka Zitting: Hi, On Feb 16, 2008 2:32 PM, Felix Meschberger [EMAIL PROTECTED] wrote: We don't walk down the tree. We currently do Session.hasItem(String) and Session.getItem(String) to find the matching item in the repository. The

[jira] Closed: (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 ] Felix Meschberger closed SLING-179. --- Resolution: Fixed Fix Version/s: 2.0.0 This is fixed as part of SLING-230.

Re: various questions regarding alternative scripting engines

Hi all, Am Freitag, den 15.02.2008, 17:42 +0100 schrieb Michael Marth: Hi Felix, when I use var node = resource.adaptTo(Packages.javax.jcr.Node) I get an exception Cannot find function adaptTo. (I guess this is a temporary problem. Or does it work for you?) Which is probably an