eXo Platform 4.0 Documentation > Reference Guide / eXo JCR > Administration > Connectors

4.1.1. WebDAV

4.1.1.1. Configuration
4.1.1.2. Examples
4.1.1.3. WebDAV and JCR commands
4.1.1.4. Restrictions
4.1.1.5. Frequently asked questions

The WebDAV protocol enables you to use third party tools to communicate with hierarchical content servers via HTTP. It is possible to add and remove documents or a set of documents from a path on the server. DeltaV is an extension of the WebDav protocol that allows managing document versioning. Locking guarantees protection against multiple access when writing resources. The ordering support allows changing the position of the resource in the list and sorts the directory to make the directory tree viewed conveniently. The fulltext search makes it easy to find the necessary documents. You can search by using two languages: SQL and XPATH.

In JCR, you plug in the WebDAV layer on the top of your JCR implementation, based on the code taken from the extension modules of the reference implementation, so it is possible to browse a workspace using third party tools (it can be Windows folders or Mac ones as well as a Java WebDAV client, such as DAVExplorer or IE using FileOpen as a Web Folder).

Now WebDAV is an extension of the REST service. To get the WebDAV server ready, you must deploy the REST application. Then, you can access any workspaces of your repository by using the following URL:

For example, when accessing the WebDAV server with the URL http://localhost:8080/portal/rest/jcr/repository/collaboration, you will be asked to enter your login and password. Those will then be checked by using the organization service that can be implemented thanks to an InMemory (dummy) module or a DB module or an LDAP one and the JCR user session will be created with the correct JCR Credentials.

Note

If you try the "in ECM" option, add "@ecm" to the user's password. Alternatively, you may modify jaas.conf by adding the domain=ecm option as follows:

exo-domain {
org.exoplatform.services.security.jaas.BasicLoginModule required domain=ecm;
};

Related documents

Copyright ©. All rights reserved. eXo Platform SAS
blog comments powered byDisqus