Hi Mike,
I cannot reproduce your problem, as you can see below. How did you configure
your stores?
Is the /history scope served by a non-memory store?
Regards,
Peter
I am using a file store configured as:
<definition>
<store name="file">
<nodestore
classname="slidestore.file.XMLFileDescriptorsStore">
<parameter
name="rootpath">{some-path}\metadatastore</parameter>
</nodestore>
<securitystore>
<reference store="nodestore"/>
</securitystore>
<lockstore>
<reference store="nodestore"/>
</lockstore>
<revisiondescriptorsstore>
<reference store="nodestore"/>
</revisiondescriptorsstore>
<revisiondescriptorstore>
<reference store="nodestore"/>
</revisiondescriptorstore>
<contentstore
classname="slidestore.reference.FileContentStore">
<parameter
name="rootpath">{some-path}\contentstore</parameter>
<parameter name="version">true</parameter>
<parameter
name="resetBeforeStarting">false</parameter>
</contentstore>
</store>
<scope match="/" store="file"/>
</definition>
Request:
REPORT /slide/files/a.xml HTTP/1.1
Content-type: text/xml; charset="utf-8"
Host: localhost:8080
Content-length: 148
<?xml version="1.0" encoding="utf-8"?>
<D:version-tree xmlns:D="DAV:">
<D:prop>
<D:predecessor-set/>
<D:successor-set/>
</D:prop>
</D:version-tree>
Response:
HTTP/1.1 207 Multi-Status
Set-Cookie: JSESSIONID=0211AB58F8BA71AAAEDC32EEBC654866; Path=/slide
Content-Type: text/xml; charset="UTF-8"
Transfer-Encoding: chunked
Date: Thu, 26 Sep 2002 08:45:48 GMT
Server: Apache Coyote/1.0
<?xml version="1.0" encoding="UTF-8"?>
<D:multistatus xmlns:D="DAV:">
<D:response>
<D:href>/slide/history/100/1.0</D:href>
<D:propstat>
<D:prop>
<D:predecessor-set />
<D:successor-set>
<D:href>/slide/history/100/1.1</D:href>
</D:successor-set>
</D:prop>
<D:status>HTTP/1.1 200 OK</D:status>
</D:propstat>
</D:response>
<D:response>
<D:href>/slide/history/100/1.1</D:href>
<D:propstat>
<D:prop>
<D:predecessor-set>
<D:href>/slide/history/100/1.0</D:href>
</D:predecessor-set>
<D:successor-set />
</D:prop>
<D:status>HTTP/1.1 200 OK</D:status>
</D:propstat>
</D:response>
</D:multistatus>
> -----Original Message-----
> From: Michael Smith [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, September 26, 2002 08:57
> To: [EMAIL PROTECTED]
> Subject: deltav bug report: <successor-set>
>
>
> Hi all,
>
> Recently discovered another bug:
> I have a resource (/files/test4.xml at the moment) with two versions:
> 1.0 and 1.1
> Doing a REPORT on this resource, I request the predecessor-set and
> successor-set.
>
> Version 1.1 has these set correctly in the response (no
> successors, and
> one predecessor - 1.0). Version 1.0, however, has neither set.
> RFC3253/3.4.2 says of the successor-set property "This property
> identifies each version whose DAV:predecessor-set identifies this
> version".
>
> My code was doing various self-consistency checks, including checking
> that a predecessor of a given version identified that version as a
> successor, so it tripped this bug. Whilst this isn't a big
> deal (my code
> at the moment uses predecessor-set in preference to successor-set
> anyway, so I can just drop the successor-set stuff entirely),
> it should
> probably get fixed eventually.
>
> Regards,
>
> Mike
>
> --
> To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
