svn commit: r1015270 - in /websites/staging/sling/trunk/content: ./ documentation/bundles/content-loading-jcr-contentloader.html

[buildbot]

Author: buildbot
Date: Tue Jul 11 15:09:56 2017
New Revision: 1015270

Log:
Staging update by buildbot for sling

Modified:
    websites/staging/sling/trunk/content/   (props changed)
    
websites/staging/sling/trunk/content/documentation/bundles/content-loading-jcr-contentloader.html

Propchange: websites/staging/sling/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Jul 11 15:09:56 2017
@@ -1 +1 @@
-1801590
+1801624

Modified: 
websites/staging/sling/trunk/content/documentation/bundles/content-loading-jcr-contentloader.html
==============================================================================
--- 
websites/staging/sling/trunk/content/documentation/bundles/content-loading-jcr-contentloader.html
 (original)
+++ 
websites/staging/sling/trunk/content/documentation/bundles/content-loading-jcr-contentloader.html
 Tue Jul 11 15:09:56 2017
@@ -394,6 +394,9 @@ primary node type "nt:file". Underneath
 
 <h3 id="extractors">Extractors<a class="headerlink" href="#extractors" 
title="Permanent link">&para;</a></h3>
 <p>By default, the <code>sling-jcr-contentloader</code> bundle tries to 
extract certain file types during content loading. These include 
<code>json</code>, <code>xml</code>, <code>zip</code>, and <code>jar</code> 
files. Therefore all available extractors are used for content processing. 
However if some files should be put into the repository unextracted, the 
<code>ignoreImportProviders</code> directive can be used with a comma separated 
list of extensions that should not be extracted, like 
<code>ignoreImportProviders:="jar,zip"</code>. Please note that the value needs 
to be put into quotation marks if more than one value is used like in the 
example.</p>
+<h3 id="file-name-escaping">File name escaping<a class="headerlink" 
href="#file-name-escaping" title="Permanent link">&para;</a></h3>
+<p>When the node name you want to import with the JCR ContentLoader contains 
characters that are not allowed in typical file systems (e.g. a ":" is not 
allowed on windows file systems), you can URL-encode the file name. It uses the 
<a 
href="https://docs.oracle.com/javase/8/docs/api/java/net/URLDecoder.html";>Java 
URLDecoder</a> internally.</p>
+<p>Example: <code>jcr%3Acontent.txt</code> will be loaded into a node named 
<code>jcr:content.txt</code>.</p>
 <h3 id="workspace-targetting">Workspace Targetting<a class="headerlink" 
href="#workspace-targetting" title="Permanent link">&para;</a></h3>
 <p>By default, initial content will be loaded into the default workspace. To 
override this, add a <code>Sling-Initial-Content-Workspace</code> bundle 
manifest header to specify the workspace. Note that <em>all</em> content from a 
bundle will be loaded into the same workspace. </p>
 <h3 id="example-load-i18n-json-files">Example: Load i18n JSON files<a 
class="headerlink" href="#example-load-i18n-json-files" title="Permanent 
link">&para;</a></h3>
@@ -469,7 +472,7 @@ Support for re-registration of node type
 <span class="p">}</span>
 </pre></div>
       <div class="timestamp" style="margin-top: 30px; font-size: 80%; 
text-align: right;">
-        Rev. 1798657 by sseifert on Wed, 14 Jun 2017 07:51:34 +0000
+        Rev. 1801624 by sseifert on Tue, 11 Jul 2017 15:09:33 +0000
       </div>
       <div class="trademarkFooter"> 
         Apache Sling, Sling, Apache, the Apache feather logo, and the Apache 
Sling project