jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Felix Meschberger <fmesc...@gmail.com>
Subject Re: WebDAV: nt:file question
Date Fri, 19 Oct 2007 15:31:06 GMT
Hi Angela,

Thanks a lot for the informations. Helps alot and of course I do not
want to change the defualt behaviour, though I think they are wrong in
terms of JCR, but this is MHO and nothing more :-)

Regards
Felix

Am Freitag, den 19.10.2007, 17:25 +0200 schrieb Angela Schreiber:
> hi felix
> 
> this has been discussed multiple times in the past.
> initially the default behaviour was exactly as you
> suggest: the jcr:content node of a default resource
> (i.e. one that is not handled by a specific handler)
> was created with nt:resource.
> 
> the drawback of the nt:resource is, that it does
> not allow to set additional (custom) properties, which
> is something people familiar with webDAV were looking for
> (and so does the litmus test suite).
> 
> -> see JCR-416
> 
> > I know, that this is perfectly "legal" but it is not expected. Rather I
> > would expect either an nt:resource node or at least a node, which has a
> > defined primary item pointing ultimately at a Property.
> 
> when looking only at the webdav functionality exposed with the
> simple server it doesn't make a difference, whether the
> jcr:content node is created with a nodetype defining a primary
> item or not: it's the responsibility of the handler to
> determine which property contains the 'data' to be exposed
> upon a GET and which properties are exposed as webdav properties.
> 
> and of cause you are free to define your own set of handlers
> that may be more restrictive or define your own nodetype that
> fits your needs.
> 
> therefore i would rather not change the default behaviour.
> 
> regards
> angela


Mime
View raw message