[
https://issues.apache.org/jira/browse/SLING-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved SLING-767.
-------------------------------------
Resolution: Fixed
Implemented this change in Rev. 725679.
Updating Documentation
> Provide better configurability and integration for WebDAV
> ---------------------------------------------------------
>
> Key: SLING-767
> URL: https://issues.apache.org/jira/browse/SLING-767
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> Affects Versions: JCR Webdav 2.0.2
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: JCR Webdav 2.0.4
>
>
> The current implementation of (simple) WebDAV support only provide little
> support for configuration of the inner operations. In addition MIME type
> resolution is not integrated with Sling support MIME type resolution.
> To fix this, Sling WebDAV should add its own configuration by means of
> extending the Jackrabbit ResourceConfig class and overwriting all methods
> along these lines:
> * MIME Type resolution is delegated to Sling's MIME type resolution by
> providing a SlingMimeResolver
> * IOManager and PropertyManager are hard coded to use the default
> implementations
> * Only DirListingExportHandler and DefaultHandler are registered and used
> * Configuration through OSGi Configuration Admin is defined.
> The following configuration is possible and supported:
> - node types defining non-collection resources
> - item filter setting by namespace uri and prefix and node type
> - node types for collection, non-collection and content nodes
> - (as before) Realm String and URL root for the separate WebDAV servlet
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
