Jan Tisje wrote: > > Hi! > > I wrote some Slide Stores and now test the behavior of some clients > using the slide webdav servlet. > > Version 0.80 of DAVexplorer could not show properties. > > Version 0.81 is a little bit better. Properties are shown correctly, > but creation does not really work for me. > > * Does WebDAV support nested properties? Slide doesn't. It saves them > serialized to a String: > <property > name="parentprop" protected="false" namespace="DAV:" value="&#10;<elem > xmlns="namespace">value</elem>&#10;" type=""/>
The WebDAV specification (http://www.ietf.org/rfc/rfc2518.txt) has samples with nested properties. However, there are lots of servers that don't support nested properties. > (the XML containing the property is generated by me) > > The property is not read back correctly. > > * Does a WebDAV property REQUIRE a separate namespace? >From a syntactical standpoint, no. But if you define new properties, it is a good idea to provide your own namespace for them. > > properties using the same (DAV:) namespace, are saved, properties with > an other namespace become a null pointer without warning. perhaps > slide is confused by the missing encoding-attribute. > > Slide client does not support specifing a namespace, DAVexp requires > one. What is correct? DAV Explorer handles displaying properties with the default namespace, it just doesn't support creating properties in the default namespace. You can, of course, use the DAV: namespace. > > btw, SkunkDAV 1.0.2.4 does not show any property contents (it shows > the names) and does not add properties. (does not send a PROPPATCH) > > Both versions of DAVexp are not able to unlock. This is a known interoperability problem. DAV Explorer does not save the lock token, instead it does a lockdiscovery. Upon a lockdiscovery, Slide returns a dummy token, which can not be used for unlock. Cheers, -Joachim -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
