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

["Bertrand Delacretaz (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bertrand Delacretaz resolved SLING-125.
---------------------------------------

    Resolution: Fixed

Implemented in revision 602100

For a Resource with sling:resourceType=/foo/bar and path=/content/blog/xyz, microsling will now look for scripts under these paths, in order:

1) /sling/scripts/foo/bar
2) /apps/foo/bar
3) /apps/blog (where "blog" is the second folder of the Resource's path)

I think we could get rid of 1), from recent discussions it seems like /apps makes more sense. But right now, this stays compatible with existing examples.

> Allow multiple script search paths + search path based on the resource path
> ---------------------------------------------------------------------------
>
>                 Key: SLING-125
>                 URL: https://issues.apache.org/jira/browse/SLING-125
>             Project: Sling
>          Issue Type: Bug
>          Components: microsling
>            Reporter: Bertrand Delacretaz
>            Priority: Minor
>
> The recently refactored ScriptSearchPathsBuilder allows for script search paths to be added easily.
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.