[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Subversion doesn't support WebDAV properties?

From: Garret Wilson <garret_at_globalmentor.com>
Date: 2007-12-29 19:08:58 CET

Hi, everyone. I asked this twice in March 2007, but no one answered. Let
me try again, because now I'm going to be working in earnest with this.

I read that Subversion versions properties just like it versions files
and directories. So using WebDAV with autoversioning turned on I decide
to add a property to http://dav.example.com/path/ . In particular, I
want to add the Dublin Core description property
<http://purl.org/dc/elements/1.1/description>. So I do a PROPPATCH:

<?xml version="1.0" encoding="UTF-8"?>
<D:propertyupdate xmlns:D="DAV:"
xmlns:dc="http://purl.org/dc/elements/1.1/">
    <D:set>
        <D:prop>
            <dc:description>New Description</dc:description>
        </D:prop>
    </D:set>
</D:propertyupdate>

Then I do a PROPFIND; Subversion returns, in part:

<?xml version="1.0" encoding="utf-8"?>
<D:multistatus xmlns:D="DAV:" xmlns:ns0="DAV:">
<D:response xmlns:S="http://subversion.tigris.org/xmlns/svn/"
xmlns:C="http://subversion.tigris.org/xmlns/custom/"
xmlns:V="http://subversion.tigris.org/xmlns/dav/" xmlns:lp1="DAV:"
xmlns:lp3="http://subversion.tigris.org/xmlns/dav/"
xmlns:lp2="http://apache.org/dav/props/">
<D:href>/path/</D:href>
<D:propstat>
<D:prop>
<C:description>New Description</C:description>
<lp1:resourcetype><D:collection/></lp1:resourcetype>
</D:prop>
<D:status>HTTP/1.1 200 OK</D:status>
</D:propstat>
</D:response>
</D:multistatus>

So Subversion has turned my WebDAV property
<http://purl.org/dc/elements/1.1/description> into
<http://subversion.tigris.org/xmlns/custom/description>. This is not good.

Question 1: Is this a bug, or is Subversion not designed to handle
custom WebDAV properties?

Question 2. If Subversion is not designed to handle custom WebDAV
properties, why doesn't it issue an error when it gets a PROPPATCH for
namespace <http://purl.org/dc/elements/1.1/> rather than automatically
converting it to some other namespace? If the client has no idea that
it's property setting didn't work, it's going to request that property
later and not receive anything---surely that's not the best course of
events. How is conversion to another namespace better than an error?

Garret

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Dec 29 19:10:49 2007

This is an archived mail posted to the Subversion Users mailing list.