[
https://issues.apache.org/jira/browse/SLING-6439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15812247#comment-15812247
]
Stefan Seifert commented on SLING-6439:
---------------------------------------
Completed: At revision: 1778016
i solved this problem in [this
rev|https://github.com/apache/sling/commit/93c427ca0e13dfd9953cfefbbfcd9048cc6b2059].
source of the problem was that [this code
line|https://github.com/apache/sling/blob/trunk/bundles/extensions/fsresource/src/main/java/org/apache/sling/fsprovider/internal/FsResource.java#L114]
did no longer have the effect as before in the old resourceresolver
implementation - it should make sure that in case of directories the resources
from fsresource provider have a lower precedence than from the JCR resource
provider.
[~cziegeler] is my solution correct according to the lastest resource resolver
impl? is the INTERNAL_CONTINUE_RESOLVING flag not working any
longer/deprecated? can you review?
> Filesystem Resource Provider 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.2
> Reporter: Stefan Seifert
> Assignee: Carsten Ziegeler
> Fix For: File System Resource Provider 1.2.2
>
>
> 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)
