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 (JIRA)" <ji...@apache.org> on 2007/12/05 22:16:43 UTC

[jira] Closed: (SLING-122) Add mechanism to access resources from places other than the repository

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

Felix Meschberger closed SLING-122.
-----------------------------------

    Resolution: Fixed

Implemented in Rev. 601511.

To make resource resolution flexible, resources are read using ResourceProvider instances. The default ResourceProvider always available is the JcrResourceManagerFactoryImpl class. Additional ReosurceProviders may be added when bundles are started which have a "Sling-Bundle-Resources" manifest header listing absolute paths of directories containing resources to be loaded from the respective bundle.

To locate a resource for a given path the resource resolver first looks for the longest matching prefix of all ResourceProviders listed and asks that resource provider for the resource. If the resource cannot be retrieved from the resource provider, the resource resolver falls back to using the default resource provider, that is looking in the repository.

See the sling/sample project for an example of the "Sling-Bundle-Resources" manifest header registering JSP source and class files accessible through the ResourceResolver. (Currently, the class file is not actually used).

> Add mechanism to access resources from places other than the repository
> -----------------------------------------------------------------------
>
>                 Key: SLING-122
>                 URL: https://issues.apache.org/jira/browse/SLING-122
>             Project: Sling
>          Issue Type: New Feature
>          Components: Content
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: 2.0.0
>
>
> Sometimes resources should be accessed which are not located in the JCR repository. An example of such resources is scripts provided by bundles, which should be executed directly out of the bundles without having to copy them into the repository. This adds support for the strong versioning and lifecylce functionality to scripts which is also available to normal bundle code.

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