Author: kwin
Date: Thu Feb 25 13:32:12 2016
New Revision: 1732300
URL: http://svn.apache.org/viewvc?rev=1732300&view=rev
Log:
some more fixes regarding headline levels
Modified:
sling/site/trunk/content/documentation/development/repository-based-development.mdtext
Modified:
sling/site/trunk/content/documentation/development/repository-based-development.mdtext
URL:
http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/development/repository-based-development.mdtext?rev=1732300&r1=1732299&r2=1732300&view=diff
==============================================================================
---
sling/site/trunk/content/documentation/development/repository-based-development.mdtext
(original)
+++
sling/site/trunk/content/documentation/development/repository-based-development.mdtext
Thu Feb 25 13:32:12 2016
@@ -2,23 +2,23 @@ Title: Repository Based Development
[TOC]
-## WebDAV Support
+# WebDAV Support
WebDAV support in Sling is based on the [Simple
WebDAV](http://jackrabbit.apache.org/jackrabbit-jcr-server.html#JackrabbitJCRServer-JCRWebdavServer)
implementation of Apache Jackrabbit which is integrated in the `jcr/webdav`
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 `/dav` in the Sling context -- and (2) access to
the workspace used by Sling itself at the root of the Sling context.
-#### Example
+## Example
Consider Sling be installed on a Servlet container in the `/sling` context on
`some.host.net:8080`. Here you would access the Sling workspace by directing
your WebDAV client to the URL `http://some.host.net:8080/sling`. To access the
`sample` workspace, which is not used by Sling itself, you would direct your
WebDAV client to the URL `http://some.host.net:8080/sling/dav/sample`.
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.
-#### Separate URI Space WebDAV
+## Separate URI Space WebDAV
When accessing the repository through WebDAV in its separate URI Space, the
URLs have the following generic structure:
- slingroot/prefix/workspace/item
+ <slingroot>/<prefix>/<workspace>/<item>
* `slingroot` is the URL of the Sling web application context. In the above
example, this would `http://some.host.net:8080/sling`.
@@ -29,7 +29,7 @@ When accessing the repository through We
If you access the WebDAV server at the prefix path -- e.g.
`!http://localhost:8080/dav` -- you will be redirected to the default workspace
with a temporary redirect status 302. Some clients, such as the Linux *davfs*,
do not like this redirection and must be configured to explicitly address the
default workspace.
-### Configuration
+## Configuration
The Jackrabbit Simple WebDAV support in Sling has the following configuration
options:
@@ -45,27 +45,27 @@ The Jackrabbit Simple WebDAV support in
| Non-Collection Primary Type | `nt:file` | The JCR Primary Node Type to
assign to nodes created to reflect WebDAV non-collection resources. You may
name any primary node type here, provided the node type is allowed to be
created below nodes of the type defined for the Collection Primary Type and
that a child node with the name "jcr:content" may be created below the
non-collection resource whose type is defined by the Content Primary Type. |
| Content Primary Type | `nt:resource` | The JCR Primary Node Type to assign
to the jcr:content child node of a WebDAV non-collection resource. You may name
any primary node type here, provided the node type is allowed to be created as
the jcr:content child node of the node type defined by the Non-Collection
Primary Type. In addition the node type must allow at least the following
properties: jcr:data (binary), jcr:lastModified (date), and jcr:mimeType
(string). |
-#### Advanced Technical Details
+## Advanced Technical Details
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:
-*IOManager*
+### IOManager
This implementation uses the standard
`org.apache.jackrabbit.server.io.IOManagerImpl` class and adds the
`org.apache.jackrabbit.server.io.DirListingExportHandler` and
`org.apache.jackrabbit.server.io.DefaultHandler` IO handlers as its only
handlers. The `DefaultHandler` is configured from the three node types listed
as configuration parameters above (collection, non-collection, and content
primary node types).
-*PropertyManager*
+### PropertyManager
This implementation uses the standard
`org.apache.jackrabbit.server.io.PropertyManagerImpl` and adds the same
`DirListingExportHandler` and `DefaultHanlder` instances as its own handlers as
are used by the IO Manager.
-*ItemFilter*
+### ItemFilter
This implementation uses the standard
`org.apache.jackrabbit.webdav.simple.DefaultItemFilter` implementation as its
item filter and configures the filter with the namespace prefixes and URIs as
well as the node types configured as parameters.
-*Collection Node Types*
+### Collection Node Types
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.
-## Eclipse plugin for JCR
+# Eclipse plugin for JCR
see [Sling IDE Tooling]({{ refs.ide-tooling.path }})
\ No newline at end of file
