You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Seifert (JIRA)" <ji...@apache.org> on 2017/01/05 20:19:58 UTC
[jira] [Commented] (SLING-6439) Filesystem Resource Provider 1.2
does not support "overlaying" nodes from repository
[ https://issues.apache.org/jira/browse/SLING-6439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15802417#comment-15802417 ]
Stefan Seifert commented on SLING-6439:
---------------------------------------
if the underlying issue is not in the fsresource provider and we do not want to support this somewhat hidden "overlaying feature" between multiple resource providers we may also implement the new feature SLING-6440 which would at least solve the problem described in this ticket in a clean way (and would provide much additional benefit as well).
> Filesystem Resource Provider 1.2 does not support "overlaying" nodes from repository
> ------------------------------------------------------------------------------------
>
> Key: SLING-6439
> URL: https://issues.apache.org/jira/browse/SLING-6439
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Affects Versions: File System Resource Provider 1.2.0
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
>
> the file system resource provider does no longer provide "overlaying" resources from the repository with resources from the filesystem. this worked with the old version 1.1.4 and was a much-used feature when mounting an maven project with content including JSON file fragements via sling content installer. in this case the bundle had to be deployed once and all binary files and content resources extracted. then, when the fsresource folder is mounted, the binary files are served from filesystem while the nodes from the JSON fragment files are still services from the repository.
> this does no longer work with the latest fsresource provider 1.2.0. perhaps the underlying issue is not the fsresource implementation, but the new sling resource provider SPI implementation.
> here is a sample project to reproduce the problem:
> https://github.com/stefanseifert/sling-fsresource-include-test
> follow the steps in the readme to reproduce the problem.
> in this branch - the only change is a switch to sling launchpad 8 and fsresource 1.1.4 - the problem does not occur:
> https://github.com/stefanseifert/sling-fsresource-include-test/tree/fsresource-1.x
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)