You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by bu...@apache.org on 2016/02/25 14:32:21 UTC
svn commit: r981139 - in /websites/staging/sling/trunk/content: ./
documentation/development/repository-based-development.html
Author: buildbot
Date: Thu Feb 25 13:32:21 2016
New Revision: 981139
Log:
Staging update by buildbot for sling
Modified:
websites/staging/sling/trunk/content/ (props changed)
websites/staging/sling/trunk/content/documentation/development/repository-based-development.html
Propchange: websites/staging/sling/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Feb 25 13:32:21 2016
@@ -1 +1 @@
-1732299
+1732300
Modified: websites/staging/sling/trunk/content/documentation/development/repository-based-development.html
==============================================================================
--- websites/staging/sling/trunk/content/documentation/development/repository-based-development.html (original)
+++ websites/staging/sling/trunk/content/documentation/development/repository-based-development.html Thu Feb 25 13:32:21 2016
@@ -119,8 +119,12 @@ h2:hover > .headerlink, h3:hover > .head
<li><a href="#webdav-support">WebDAV Support</a><ul>
<li><a href="#example">Example</a></li>
<li><a href="#separate-uri-space-webdav">Separate URI Space WebDAV</a></li>
-<li><a href="#configuration">Configuration</a><ul>
-<li><a href="#advanced-technical-details">Advanced Technical Details</a></li>
+<li><a href="#configuration">Configuration</a></li>
+<li><a href="#advanced-technical-details">Advanced Technical Details</a><ul>
+<li><a href="#iomanager">IOManager</a></li>
+<li><a href="#propertymanager">PropertyManager</a></li>
+<li><a href="#itemfilter">ItemFilter</a></li>
+<li><a href="#collection-node-types">Collection Node Types</a></li>
</ul>
</li>
</ul>
@@ -128,14 +132,14 @@ h2:hover > .headerlink, h3:hover > .head
<li><a href="#eclipse-plugin-for-jcr">Eclipse plugin for JCR</a></li>
</ul>
</div>
-<h2 id="webdav-support">WebDAV Support<a class="headerlink" href="#webdav-support" title="Permanent link">¶</a></h2>
+<h1 id="webdav-support">WebDAV Support<a class="headerlink" href="#webdav-support" title="Permanent link">¶</a></h1>
<p>WebDAV support in Sling is based on the <a href="http://jackrabbit.apache.org/jackrabbit-jcr-server.html#JackrabbitJCRServer-JCRWebdavServer">Simple WebDAV</a> implementation of Apache Jackrabbit which is integrated in the <code>jcr/webdav</code> project. This bundle provides WebDAV access to Sling's repository in two flavours: (1) Access to all workspaces of the repository on a separate URL space -- by default rooted at <code>/dav</code> in the Sling context -- and (2) access to the workspace used by Sling itself at the root of the Sling context.</p>
-<h4 id="example">Example<a class="headerlink" href="#example" title="Permanent link">¶</a></h4>
+<h2 id="example">Example<a class="headerlink" href="#example" title="Permanent link">¶</a></h2>
<p>Consider Sling be installed on a Servlet container in the <code>/sling</code> context on <code>some.host.net:8080</code>. Here you would access the Sling workspace by directing your WebDAV client to the URL <code>http://some.host.net:8080/sling</code>. To access the <code>sample</code> workspace, which is not used by Sling itself, you would direct your WebDAV client to the URL <code>http://some.host.net:8080/sling/dav/sample</code>.</p>
<p>Please note that accessing the repository in the separate URI space is actually faster, since requests do not pass the Sling resource and script resolution framework but instead hit the Jackrabbit Simple WebDAV Servlet directly.</p>
-<h4 id="separate-uri-space-webdav">Separate URI Space WebDAV<a class="headerlink" href="#separate-uri-space-webdav" title="Permanent link">¶</a></h4>
+<h2 id="separate-uri-space-webdav">Separate URI Space WebDAV<a class="headerlink" href="#separate-uri-space-webdav" title="Permanent link">¶</a></h2>
<p>When accessing the repository through WebDAV in its separate URI Space, the URLs have the following generic structure:</p>
-<div class="codehilite"><pre><span class="n">slingroot</span><span class="o">/</span><span class="n">prefix</span><span class="o">/</span><span class="n">workspace</span><span class="o">/</span><span class="n">item</span>
+<div class="codehilite"><pre><span class="o"><</span><span class="n">slingroot</span><span class="o">>/<</span><span class="n">prefix</span><span class="o">>/<</span><span class="n">workspace</span><span class="o">>/<</span><span class="n">item</span><span class="o">></span>
</pre></div>
@@ -146,7 +150,7 @@ h2:hover > .headerlink, h3:hover > .head
<li><code>item</code> is the path to the JCR Item to access.</li>
</ul>
<p>If you access the WebDAV server at the prefix path -- e.g. <code>!http://localhost:8080/dav</code> -- you will be redirected to the default workspace with a temporary redirect status 302. Some clients, such as the Linux <em>davfs</em>, do not like this redirection and must be configured to explicitly address the default workspace.</p>
-<h3 id="configuration">Configuration<a class="headerlink" href="#configuration" title="Permanent link">¶</a></h3>
+<h2 id="configuration">Configuration<a class="headerlink" href="#configuration" title="Permanent link">¶</a></h2>
<p>The Jackrabbit Simple WebDAV support in Sling has the following configuration options:</p>
<table class="table">
<thead>
@@ -204,20 +208,20 @@ h2:hover > .headerlink, h3:hover > .head
</tr>
</tbody>
</table>
-<h4 id="advanced-technical-details">Advanced Technical Details<a class="headerlink" href="#advanced-technical-details" title="Permanent link">¶</a></h4>
+<h2 id="advanced-technical-details">Advanced Technical Details<a class="headerlink" href="#advanced-technical-details" title="Permanent link">¶</a></h2>
<p>Since the Jackrabbit Simple WebDAV Servlet is originally configured using an XML configuration file, which provides a great deal of flexibility, the integration into Sling had to assume some simplifications, of which some of the above parameters are part:</p>
-<p><em>IOManager</em></p>
+<h3 id="iomanager">IOManager<a class="headerlink" href="#iomanager" title="Permanent link">¶</a></h3>
<p>This implementation uses the standard <code>org.apache.jackrabbit.server.io.IOManagerImpl</code> class and adds the <code>org.apache.jackrabbit.server.io.DirListingExportHandler</code> and <code>org.apache.jackrabbit.server.io.DefaultHandler</code> IO handlers as its only handlers. The <code>DefaultHandler</code> is configured from the three node types listed as configuration parameters above (collection, non-collection, and content primary node types).</p>
-<p><em>PropertyManager</em></p>
+<h3 id="propertymanager">PropertyManager<a class="headerlink" href="#propertymanager" title="Permanent link">¶</a></h3>
<p>This implementation uses the standard <code>org.apache.jackrabbit.server.io.PropertyManagerImpl</code> and adds the same <code>DirListingExportHandler</code> and <code>DefaultHanlder</code> instances as its own handlers as are used by the IO Manager.</p>
-<p><em>ItemFilter</em></p>
+<h3 id="itemfilter">ItemFilter<a class="headerlink" href="#itemfilter" title="Permanent link">¶</a></h3>
<p>This implementation uses the standard <code>org.apache.jackrabbit.webdav.simple.DefaultItemFilter</code> implementation as its item filter and configures the filter with the namespace prefixes and URIs as well as the node types configured as parameters.</p>
-<p><em>Collection Node Types</em></p>
+<h3 id="collection-node-types">Collection Node Types<a class="headerlink" href="#collection-node-types" title="Permanent link">¶</a></h3>
<p>This implementation only supports listing node types which are considered representing non-collection resources. All nodes which are instances of any of the configured node types are considered non-collection resources. All other nodes are considere collection resources.</p>
-<h2 id="eclipse-plugin-for-jcr">Eclipse plugin for JCR<a class="headerlink" href="#eclipse-plugin-for-jcr" title="Permanent link">¶</a></h2>
+<h1 id="eclipse-plugin-for-jcr">Eclipse plugin for JCR<a class="headerlink" href="#eclipse-plugin-for-jcr" title="Permanent link">¶</a></h1>
<p>see <a href="/documentation/development/ide-tooling.html">Sling IDE Tooling</a></p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
- Rev. 1732299 by kwin on Thu, 25 Feb 2016 13:28:21 +0000
+ Rev. 1732300 by kwin on Thu, 25 Feb 2016 13:32:12 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project