jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kevin Jansz <kevin.ja...@exari.com>
Subject Re: choosing a WebdavServlet implementation
Date Thu, 16 Sep 2010 23:18:35 GMT
many thanks, exactly what I was looking for (didn't expect to find it
in the docs).

--
Kevin Jansz
kevin.jansz@exari.com
Level 7, 10-16 Queen Street, Melbourne 3000 Australia
Tel +61 3 9621 2773 | Fax +61 3 9621 2776
Exari Systems
Boston | London | Melbourne | Munich
www.exari.com

Test drive our software online - www.exari.com/demo-trial.html
Read our blog on document assembly - blog.exari.com




On 16 September 2010 22:28, Jukka Zitting <jukka.zitting@gmail.com> wrote:
> Hi,
>
> On Thu, Sep 16, 2010 at 8:19 AM, Kevin Jansz <kevin.jansz@exari.com> wrote:
>> The org.apache.jackrabbit.j2ee.JCRWebdavServerServlet seems to expose
>> the full details of the resources but not in the way I'd expect - eg
>> can't seem to get the content via GET file_path or GET
>> file_path/jcr:content.
>
> See http://jackrabbit.apache.org/jackrabbit-jcr-server.html and the
> attached JCR_Webdav_Protocol.doc file for a detailed description of
> the JCRWebdavServerServlet functionality.
>
>> Is the idea that developers use SimpleWebdavServlet &
>> JCRWebdavServerServlet as the basis for building their own
>> implementation to their requirements (extending
>> AbstractWebdavServlet?).
>
> Depends on your needs. For simple extensions you should be using the
> IOHandler mechanism defined in the jackrabbit-jcr-server component.
>
> BR,
>
> Jukka Zitting
>

Mime
View raw message