Apparently, when obtaining revision information, a lockcheck is required. If there isn't a principal associated to the client, then the lock check fails (no user to do a role check against). The JBoss login module I submitted to the list previous to this email allows me to authenticate and now see the revisions and content for files submitted to Slide (even via Microsoft web folders).
As a followup question then, why is the lock check required for obtaining revision info for a file? Is this something in the spec I don't understand or just something that was determined necessary to the internals of Slide? Thanks, James > -----Original Message----- > From: James Higginbotham > Sent: Monday, February 24, 2003 7:19 AM > To: Slide Users Mailing List > Subject: RE: Versioning woes > > > Thanks Martin and Peter for your quick responses.. After some > further debugging, I've found the following issues: > > 1) It seems that lockHelper.checkLock() doesn't honor the > xxx.xxx.security=false property, so its failing and throwing > an exception > 2) The tags seem to want to use the Delta/V revisions, as if > this check would pass, it would call revisionDescriptors = > objectUri.getStore().retrieveRevisionDescriptors(objectUri); > 3) Not sure what this means (ContentImpl:204): > // FIXME: createRevisionDescriptors shouldn't be > done in this read-only method > objectUri.getStore() > .createRevisionDescriptors(objectUri, > revisionDescriptors); > > I'll look into how much work it would take to make the lock > helper support the flag, followed by turning on auth if that > seems to be too tough (shouldn't be, it's a props file!) > > Best Regards, > James > > > > > -----Original Message----- > > From: Nevermann, Dr., Peter [mailto:[EMAIL PROTECTED] > > Sent: Monday, February 24, 2003 6:27 AM > > To: 'Slide Users Mailing List' > > Subject: RE: Versioning woes > > > > > > > I have been using a daily build from Nov 13th and just > > upgraded to the > > > Feb 23rd daily build.. When using either memory or hsql stores for > > > either version, I cannot seem to get the versioning to show > > up using > > > the struts tag lib "slide:node" tag. All I see is a node > that says > > > versioned == false, and the list of revisions returned from the > > > taglib is empty.. > > > Since this is happening, I cannot pull the content back for > > the latest > > > revision using the tags, nor the properties for the latest > > > revision. > > > > I'm not very aware of the taglib, but as far as I could see, > > the taglib accesses directly the, let me call it "Slide Core > > API", i.e. the layer of the "helpers". As DeltaV is mainly > > implemented in the WebDAV layer, the taglib probably is not > > yet able to access the DeltaV-related data. > > Example: if you are accessing a DeltaV-versioned resource at > > /files/foo.txt (a VCR in DeltaV terminology), this resource - > > viewed as Slide resource - is > > *not* versioned. The list of revisions is in the associated > > *history* resource (the VHR) at, say, /history/17. The URI of > > the history resource can be derived from the value of the > > DAV:checked-in property of VCR. > > > > > So, I am assuming: > > > > > > 1) That versioning isn't working.. I don't believe this > is the case, > > > as I've turned it on in the Domain.xml and I am seeing > files showing > > > up under the history directory.. I don't have a Delta/V client > > other than > > > the web interface I'm building and any metadata SkunkDAV is > > seeing... > > > Any good windows clients out there that support Delta/V I can > > > use to try > > > and confirm this possible bug? > > > > Try either of the following FREE protocol-level tools: > "Tamino WebDAV > > BasicClient 1.1.1" at: > > http://developer.softwareag.com/tamino/webdav/default.htm > > or > > "NetTool" at: > > http://sourceforge.net/project/showfiles.php?group_id=55568&re > > lease_id=11544 > > 4 > > > > I can recommend the 1st one :-). > > > > > 4) Versioning doesn't work without security being turned > on - I have > > > it turned off for now for quicker development > > > > By "without security" do you mean that you switched-off > > authentication in web.xml? I tried that but didn't get any > > problems. Could you please send details (stack traces, log > > files, etc.)? > > > > > I am seeing the following properties via SkunkDAV: > > > > > > host localhost > > > port 8080 > > > name > > /slide/files/sites/www.calvaryaustin.org/xml/homepage/home.xml > > > creation date 2003-02-24T01:09:49Z > > > last modified date Mon, 24 Feb 2003 01:09:49 GMT > > > content type text/xml > > > content length 405 > > > content language en > > > display name home.xml > > > resource type > > > etag 397939377_48563_405 > > > supported locks Lock [scope=exclusive, type=write], > > > Lock [scope=shared, > > > type=write] > > > active locks > > > links > > > > > > Should I be seeing some properties related to versioning at all? > > > > No, as specified in the RFC 3253 (DeltaV), the DeltaV-related > > properties are not shown in a DAV:allprop PROPFIND request > > and are to be requested explicitly. However, for testing > > purposes, you can enable the "allpropIncludesDeltav" > > init-parameter of the WebDAV servlet in web.xml. > > > > BTW, your Domain.xml looks fine. > > > > Regards, > > Peter > > > > > --------------------------------------------------------------------- > > 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]
