Good man nonetheless. Michael Oliver CTO Matrix Intermedia Inc. 3325 N. Nellis Blvd, #1 Las Vegas, NV 89115 Phone:(702)643-7425 Fax:(520)844-1036
-----Original Message----- From: James Mason [mailto:[EMAIL PROTECTED] Sent: Monday, July 19, 2004 9:50 AM To: [EMAIL PROTECTED] Subject: RE: How to find out about roles ? Well, it turns out the resourceType is handled by a different class (subclass of BaseProperty) so there's still a problem there. It only handles <collection/>. There's a FIXME note in the source, though... ;). -James >>> [EMAIL PROTECTED] 7/17/2004 8:22:45 AM >>> Good man! I am guessing you fixed the "resourceType" similar problem too??? ;-)> I will dance at your next wedding. Michael Oliver CTO Matrix Intermedia Inc. 3325 N. Nellis Blvd, #1 Las Vegas, NV 89115 Phone:(702)643-7425 Fax:(520)844-1036 -----Original Message----- From: James Mason [mailto:[EMAIL PROTECTED] Sent: Friday, July 16, 2004 3:54 PM To: [EMAIL PROTECTED] Subject: RE: How to find out about roles ? Michael, Point taken :). I just checked in a patch that makes the command-line client display properties with XML data. It's not perfect, if the content is mixed xml and text the ordering is going to be wrong, but as long as any xml data is in a root node it should work find. -James >>> [EMAIL PROTECTED] 7/16/2004 12:51:57 PM >>> James, The point wasn't that the Client Library (i.e. WebdavResource) or some other client couldn't get the property. It was that the Command Line Client couldn't and it can't without modification and DAV Explorer 0.90 doesn't either BTW. I am not trying to start a flame war, just trying to be clear. Michael Oliver CTO Matrix Intermedia Inc. 3325 N. Nellis Blvd, #1 Las Vegas, NV 89115 Phone:(702)643-7425 Fax:(520)844-1036 -----Original Message----- From: James Mason [mailto:[EMAIL PROTECTED] Sent: Friday, July 16, 2004 12:33 PM To: [EMAIL PROTECTED] Subject: RE: How to find out about roles ? Well, technically, the data is reaching the client, so you are retrieving it ;). The trick is finding a client that will actually display the information. I think the command-line client just doesn't handle outputting xml. I've seen the same problem looking at the resource-type property, for example. -James >>> [EMAIL PROTECTED] 7/16/2004 12:12:25 PM >>> James where does "*can*" == "it doesn't output them at all."??? Michael Oliver CTO Matrix Intermedia Inc. 3325 N. Nellis Blvd, #1 Las Vegas, NV 89115 Phone:(702)643-7425 Fax:(520)844-1036 -----Original Message----- From: James Mason [mailto:[EMAIL PROTECTED] Sent: Friday, July 16, 2004 12:00 PM To: [EMAIL PROTECTED] Subject: RE: How to find out about roles ? You *can* retrieve this property using a WebDAV client, the problem is that the command-line client doesn't output properties that contain xml properly. In fact, it doesn't output them at all. It just spits out a long, empty string. One thing to note is the group-member-set property is not returned with a propgetall response (for performance reasons). I believe you can modify this in the web.xml file for the webdav servlet. That would allow you to use a client that displays xml property but can't issue a propget request for a single property (like DAV Explorer) to maintain that property. -James >>> [EMAIL PROTECTED] 7/16/2004 8:25:17 AM >>> > Roles have the "group-member-set" property, its value contains > URIs of all users that belong to this role. Do they? But I can not find this property. e.g. if I look with the commandline client for "propget /slide/roles/manager displayname" it returns "manager" but if I look for "propget /slide/roles/manager group-member-set" it returns an empty String. also the article on the slide website told, that this property is not visible via webdav. why??? How else should roles be handled then? Frank --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
