Bug 29081 - WebdavResource.getIsHidden() is never true
Summary: WebdavResource.getIsHidden() is never true
Status: NEW
Alias: None
Product: Slide
Classification: Unclassified
Component: WebDAV Server (show other bugs)
Version: 2.1
Hardware: PC Linux
: P3 minor (vote)
Target Milestone: ---
Assignee: Slide Developer List
URL:
Keywords:
Depends on:
Blocks: 31521
  Show dependency tree
 
Reported: 2004-05-19 10:58 UTC by Rob Leathley
Modified: 2004-11-16 19:05 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rob Leathley 2004-05-19 10:58:40 UTC
resource.getIsHidden() returns false,

even when the following returns true:

Enumeration e = resource.propfindMethod("ishidden");
if (e.hasMoreElements())
  isHidden = ((String) e.nextElement()).equals("1");

Which is very similar to what is in WebdavResource.java.

There is also no public method resource.setIsHidden(boolean isHidden) to change
this property so I am using resource.proppatchMethod.
Comment 1 Ingo Brunberg 2004-05-19 11:41:13 UTC
Does anyone know something about a "ishidden" property? It's not mentioned in
the WebDAV specification. Is there some server that automatically generates such
a property?

I guess that method should have served as the basis for the isHidden() method in
WebdavFile. But in my opinion isHidden() is not applicable to a WebDAV
repository in general, so it's reasonable to always return false. This means
that isHidden related methods should be removed from WebdavResource.

Other opinions?
Comment 2 Rob Leathley 2004-05-19 12:26:08 UTC
Maybe it should be removed from WebdavResource.  I only tried using it because
it appeared here.  I couldn't find any reference in the spec either.
Comment 3 Daniel Florey 2004-06-05 09:21:56 UTC
The ishidden-property is a microsoft extension specified in the following 
draft:

http://greenbytes.de/tech/webdav/draft-hopmann-collection-props-00.txt

We should try to support the added properties in order to improve the MS 
Office/Webfolder interoperability.
This no bug, so I adressed this to the 2.1 release