[
https://issues.apache.org/jira/browse/SLING-4538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14377559#comment-14377559
]
Radu Cotescu commented on SLING-4538:
-------------------------------------
I tried the trunk version. The culprit is here:
https://github.com/apache/sling/blob/trunk/bundles/jcr/contentloader/src/main/java/org/apache/sling/jcr/contentloader/internal/BundleContentLoader.java#L409
The content reader is obtained based solely on path (now named entry), without
taking into account the configuration, which might specify that some import
providers should be ignored.
> Content loaders cannot be ignored any more
> ------------------------------------------
>
> Key: SLING-4538
> URL: https://issues.apache.org/jira/browse/SLING-4538
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Reporter: Radu Cotescu
> Assignee: Radu Cotescu
> Fix For: JCR ContentLoader 2.2.0
>
>
> Changes proposed in SLING-4223 don't allow content loaders to be ignored any
> more, which was a major feature of the {{org.apache.sling.jcr.contentloader}}
> bundle. As an example, XML files cannot be currently imported as binary files
> using the Sling Initial Content mechanism, as they're treated as content
> descriptors.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)