You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jackrabbit.apache.org by Kevin Jansz <ke...@exari.com> on 2010/09/16 07:19:51 UTC
choosing a WebdavServlet implementation
Working on a solution that has utilised Slide in the past, I'd been
testing with org.apache.jackrabbit.j2ee.SimpleWebdavServlet in the
jackrabbit webapp and it's been fine for managing the resources over
WebDAV as if they were files and folders. I've now hit limitations
with trying to access information about Versions and ACLs over WebDAV
and was hoping to get advice ...
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.
Is the idea that developers use SimpleWebdavServlet &
JCRWebdavServerServlet as the basis for building their own
implementation to their requirements (extending
AbstractWebdavServlet?).
thanks
--
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
Re: choosing a WebdavServlet implementation
Posted by Kevin Jansz <ke...@exari.com>.
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 <ju...@gmail.com> wrote:
> Hi,
>
> On Thu, Sep 16, 2010 at 8:19 AM, Kevin Jansz <ke...@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
>
Re: choosing a WebdavServlet implementation
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Thu, Sep 16, 2010 at 8:19 AM, Kevin Jansz <ke...@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