[ 
http://issues.apache.org/jira/browse/JCR-179?page=comments#action_12318283 ] 

Brian Moseley commented on JCR-179:
-----------------------------------

it turns out that i was in fact using cadaver correctly. cadaver's default 
namespace is "DAV:", which of course is not registered in the repository. so 
the webdav server was throwing a NamespaceException when trying to formulate 
the jcr name for "DAV:hi". cadaver didn't report the response description to me 
until i figured out how to turn on http-level debugging.

the correct way to set the property is to set the cadaver namespace to be one 
that is registered in the repository, then create the property in that 
namespace:

dav:/home/> set namespace http://osafoundation.org/jcr/dav/1.0
dav:/home/> propset hi myprop abc123
dav:/home/> propget hi myprop
Value of myprop is: abc123

this begs the question: since webdav servers are required by rfc 2518 to store 
the values of dead properties, shouldn't jcr-server attempt to register unknown 
namespaces rather than returning 403 Forbidden?

> PROPPATCH in simple webdav server failing with 403 Forbidden error
> ------------------------------------------------------------------
>
>          Key: JCR-179
>          URL: http://issues.apache.org/jira/browse/JCR-179
>      Project: Jackrabbit
>         Type: Bug
>     Reporter: Brian Moseley

>
> i've configured the import-collection chain (called via MKCOL) to add nodes 
> with the node type "dav:collection", which is defined as such:
> NodeTypeName
>   dav:collection
> SuperTypes
>   nt:folder
> IsMixin
>   false
> HasOrderableChildNodes
>   false
> PrimaryItemName
>   null
> PropertyDef
>   Name *
>   RequiredType UNDEFINED
>   DefaultValues null
>   AutoCreate false
>   Mandatory false
>   OnParentVersion COPY
>   Protected false
>   Multiple false
> PropertyDef
>   Name *
>   RequiredType UNDEFINED
>   DefaultValues null
>   AutoCreate false
>   Mandatory false
>   OnParentVersion COPY
>   Protected false
>   Multiple true
> the idea is that i should be able to set arbitrary webdav properties (single- 
> or multi-value) on a webdav collection.
> when i use cadaver to mkcol a collection (creating a jcr node of type 
> dav:collection) and then try to propset an arbitrary property on that 
> collection (which as i understand it would set a jcr property of the same 
> name on the dav:collection node), i get a 403 Forbidden error:
> dav:/home/> mkcol hi
> Creating `hi': succeeded.
> dav:/home/> propset hi hi hi
> Setting property on `hi': failed:
> 403 Forbidden
> it's not clear to me if i'm using cadaver incorrectly, misunderstanding the 
> PROPPATCH implementation, or both :) 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Reply via email to