Hi Peter!

Thank you for the replies! I tried the XMLFileDescriptorsStore as you
suggested and the problem went away! I guess it was store specific!! 

/Jacob

-----Original Message-----
From: Nevermann, Dr., Peter [mailto:[EMAIL PROTECTED]] 
Sent: 23. september 2002 16:53
To: 'Slide Users Mailing List'
Subject: RE: Successor-set missing


You are right, the DeltaV spec states that the property
DAV:successor-set is computed.

I guess that the problem in your config could be that the /history scope
is not explicitly configured and therefore maybe served by the memory
store. So, when you restart the server all required history data to
compute DAV:successor-set would be lost.

When I use the file store my config looks like:

    <definition>
        <store name="file">
                <nodestore
classname="slidestore.file.XMLFileDescriptorsStore">
                        <parameter
name="rootpath">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">contentstore</parameter>
                        <parameter name="version">true</parameter>
                        <parameter
name="resetBeforeStarting">false</parameter>
                </contentstore>
        </store>
        <scope match="/" store="file"/>
    </definition>

So, the file store serves also the /history scope in this case. And I
cannot reproduce your problem with that config.

Regards,
Peter

> -----Original Message-----
> From: Jacob Lund [mailto:[EMAIL PROTECTED]]
> Sent: Monday, September 23, 2002 16:29
> To: 'Slide Users Mailing List'
> Subject: RE: Successor-set missing
> 
> 
> I was using a relational descriptors store - I did not know this was 
> store specific. I thought the successor-set was a computed value and 
> not something stored in the db. I know this relational store has some
> problems - I will try another store and report back!
> 
> Thanks
> Jacob
> 
> -----Original Message-----
> From: Nevermann, Dr., Peter [mailto:[EMAIL PROTECTED]]
> Sent: 23. september 2002 14:58
> To: 'Slide Users Mailing List'
> Subject: RE: Successor-set missing
> 
> 
> Hi Jacob,
> which stores have you configured in your Domain.xml?
> Regards,
> Peter
>  
> 
> > -----Original Message-----
> > From: Jacob Lund [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, September 23, 2002 11:35
> > To: [EMAIL PROTECTED]
> > Subject: Successor-set missing
> > 
> > 
> > Hi,
> > 
> > I am trying to do a DAV:version-tree report!
> > 
> > I create a new resource on the server and do a couple of 
> > checkout/checkin to create a couple of revisions of the resource!
> > 
> > I then request a REPORT on the resource with the following body:
> > 
> > <?xml version=\"1.0\" encoding=\"utf-8\"?>
> > <D:version-tree xmlns:D='DAV:'>
> > <D:prop>
> > <D:version-name/>
> > <D:creator-displayname/>
> > <D:successor-set/>
> > </D:prop>
> > </D:version-tree>
> > 
> > (Example taken from the DeltaV documentation)
> > 
> > Then I get a nice report back with correct data, but if I
> then restart
> > the server the successor-set disappears!! If I then create a new
> > revision of the resource and run the report request again then the 
> > successor-set for the previous revision will point to the 
> new revision
> 
> > but the others still have an empty successor-set?
> > 
> > Is this a bug or am I missing something?
> > 
> > /Jacob
> > 
> > 
> > --
> > 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]>
> 
> 
> --
> 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]>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to