The value we see in DAV for the property is the updated value.
Reinier
Ard Schrijvers wrote:
Hello Reinier,
Hopefully you can test one more thing for me (and then I fully do
believe it is a caching bug, though it must be in the Repository Adapter
then, a tool I am not to familiar with (more with cocoon's cache) but I
should be able to reproduce it then and fix it). So the thing you might
want to test for me:
If in the frontend, the property date is not equal to the date in the
document (which might thus indicate only partial invalidation worked, in
other words, only the document itself invalidated (though, without
knowing the repo adapter I can hardly imagine how... :-) )) and not the
property. Now, if, after you have this situation, you can browse the
repository with something like webdav pilot, and look at the webdav
property on the document. Can you confirm that this is the correct
webdav property, thus the changed value. If so, I need to look at the
adapter invalidation mechanism,
Regards Ard
Hi Ard,
In addition to my previous answer (I get my info from the guy
that did the implementation, so there is a bit of delay on
the line :-)
We have printed the date as it is in the document together
with the extracted property next to each other. Normally they
are identical. It proved that after modifying the document
they would differ: the property showing the old value.
A restart of tomcat would sync them again.
Reinier
Ard Schrijvers wrote:
Hello,
The frontend you describe is an extended cms, a cocoon
frontend or a
other frontend?
How is the property containing the date called? How do you
store this
date? Something like 20080702 or in a more Date like format? If the
latter, you need to add this property to be 'date' indexed to the
indexing.xml configuration of the repository. Can you tell me the
format you store the property in.
It does not seem to me to be a caching issue, because the frontend
result seems to be invalidated and rendered (improperly
though) again,
right?
Furthermore, can you show me the dasls which should do the
sorting? I
have used things like this really many times, so sorting should
definitely work. Pls provide the information asked for and
I'll take a
look,
Regards Ard
Hi all,
We experience a problem that seems to have to do with caching and
DASL queries.
Situation:
We have documents containing a date. The date is extracted
and turned
into a DAV property. Documents are organised in folders.
We have three pages that list documents.
One lists all docs within a folder. This uses a simple DASL-query.
The other two list a subset of all documents ordered on this date.
These pages use a similar query but with a sort (on
date) and a limit (first 20 or so).
There are several problems:
When we add a new document, it rarely shows up on any of the pages.
When we change a date, the new date is shown in the
listing, but the
list is not sorted accordingly. This differs per
page: the full listing usually is correct, but the limited
listings
are in the wrong order.
When we reset everything (repo+frontend), everything is as
expected.
We have two installation: one running repo on jetty and
frontend on
tomcat, other running both on tomcat. Problems are more or
less the
same on either installation.
(on jetty we used repo: 1.2.14.rc1 and 1.2.15.1, on tomcat only
1.2.14.rc1)
Any ideas?
Thanks,
Reinier
--
Reinier van den Born
HintTech B.V.
Rotterdamseweg 183c, 2629 HD Delft
T: +31(0)15 268 2573
F: +31(0)15 268 2567
M: +31(0)6 494 171 36
--
HintTech levert specialisten op het gebied van
softwareontwikkeling
(.NET en Java), projectmanagement, informatiebeveiliging
en business
consulting.
KvK Den Haag nr. 27242282 | BTW nr. NL8062.16.396.B01
********************************************
Hippocms-dev: Hippo CMS development public mailinglist
Searchable archives can be found at:
<a href=ttp://hippocms-dev.markmail.org/">MarkMail</a> and
<a href="http://www.nabble.com/Hippo-CMS-f26633.html";>Nable</a>.
--
Reinier van den Born
HintTech B.V.
Rotterdamseweg 183c, 2629 HD Delft
T: +31(0)15 268 2573
F: +31(0)15 268 2567
M: +31(0)6 494 171 36
--
HintTech levert specialisten op het gebied van
softwareontwikkeling (.NET en Java), projectmanagement,
informatiebeveiliging en business consulting.
KvK Den Haag nr. 27242282 | BTW nr. NL8062.16.396.B01
********************************************
Hippocms-dev: Hippo CMS development public mailinglist
Searchable archives can be found at:
MarkMail: http://hippocms-dev.markmail.org
Nabble: http://www.nabble.com/Hippo-CMS-f26633.html
--
Reinier van den Born
HintTech B.V.
Rotterdamseweg 183c, 2629 HD Delft
T: +31(0)15 268 2573
F: +31(0)15 268 2567
M: +31(0)6 494 171 36
--
HintTech levert specialisten op het gebied van softwareontwikkeling (.NET en
Java),
projectmanagement, informatiebeveiliging en business consulting.
KvK Den Haag nr. 27242282 | BTW nr. NL8062.16.396.B01
begin:vcard
fn:Reinier van den Born
n:van den Born;Reinier
org:HintTech B.V.
adr:;;Rotterdamseweg 183c;Delft;;2629HD;Netherlands
email;internet:[EMAIL PROTECTED]
tel;work:+31-15-268 2573
tel;fax:+31-15-268 2567
tel;cell:+31-6 494 171 36
note;quoted-printable:KvK Den Haag nr. 27242282 | BTW nr. NL8062.16.396.B01=0D=0A=
=0D=0A=
HintTech levert specialisten op het gebied van softwareontwikkeling (.NET=
en Java), projectmanagement, informatiebeveiliging en business consulting=
.=0D=0A=
=0D=0A=
url:www.hinttech.com
version:2.1
end:vcard
********************************************
Hippocms-dev: Hippo CMS development public mailinglist
Searchable archives can be found at:
MarkMail: http://hippocms-dev.markmail.org
Nabble: http://www.nabble.com/Hippo-CMS-f26633.html
