You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by Felix Meschberger <fm...@gmail.com> on 2007/12/10 10:23:08 UTC

Re: [jira] Created: (SLING-125) Allow multiple script search paths + search path based on the resource path

Hi,

Am Freitag, den 07.12.2007, 05:02 -0800 schrieb Bertrand Delacretaz
(JIRA):
> One interesting feature would to use an additional search path that depends on the beginning of the resource path, for example for a resource found at
> 
>   /content/blog/a/b/c
> 
> we'd look for scripts under
> 
>   /apps/blog
> 
> in addition to the default location.This allows microsling to run on repositories that already contain data which doesn't have a sling:resourceType property, without having to resort to nodetype-based mapping.
> 
> I'll implement that without breaking compatibility, and we can play with it and see if it's useful.

The questions are :

* Is this just interesting or do we have a use case ?

* What happens if you move the resource to, say, /content/quark/a/b/c ?

* Who defines what the "beginning of the resource path" is ?

At the moment I am rather sceptical, whether this is actually a good
idea :-)

Regards
Felix


Re: [jira] Created: (SLING-125) Allow multiple script search paths + search path based on the resource path

Posted by Bertrand Delacretaz <bd...@apache.org>.
On Dec 10, 2007 10:23 AM, Felix Meschberger <fm...@gmail.com> wrote:
> Hi,
>
> Am Freitag, den 07.12.2007, 05:02 -0800 schrieb Bertrand Delacretaz
> > One interesting feature would to use an additional search path that depends on the beginning of the resource path, for example for a resource found at
> >   /content/blog/a/b/c
> > we'd look for scripts under
> >   /apps/blog...

> ...The questions are :
>
> * Is this just interesting or do we have a use case ?

See my upcoming "chickens, eggs and stars" post, there are several
interrelated issues here.

>
> * What happens if you move the resource to, say, /content/quark/a/b/c ?

That would break the link between content and scripts, of course.

>
> * Who defines what the "beginning of the resource path" is ?

currently in the /apps/XX path, XX is the second level of the resource
path, see ScriptSearchPathsBuilder

> ...At the moment I am rather sceptical, whether this is actually a good
> idea :-)...

I understand, I'll explain more shortly.

-Bertrand