Hi Ard,
We are using an extended CMS and a JSP/HST frontend.
The date is extracted using following extractor:
<extractor
classname="nl.hippo.slide.extractor.HippoSimpleXmlExtractor"
uri="/files/default.preview/content/e-overheid/nieuws"
content-type="text/xml">
<configuration>
<instruction property="contentDate"
namespace="http://hippo.nl/cms/1.0";
xpath="/document/content/date/text()" />
</configuration>
</extractor>
Simply gets a text field from the document.
I attached two DASLs: one that works, another that doesn't.
The reason that we think it is a caching problem, is that after we
restart tomcat (runs CMS, repo, and frontend) suddenly everything is
fine... In other words the result of the DASL is not consistent.
The document gets invalidated because we see the new date appear, that
is true. The date from the document, not the extracted property. I'll
see if we can print the latter too, maybe that tells us more.
The feeling I get is that document properties or DASL results are cached
separately. Is anything like that going on, or can I put that straight
out of my head?
Thanks,
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
<d:searchrequest xmlns:d="DAV:" xmlns:slide="http://jakarta.apache.org/slide/";
xmlns:h="http://hippo.nl/cms/1.0";>
<d:basicsearch>
<d:select>
<d:prop>
<h:caption/>
<d:displayname/>
<h:index/>
<h:type/>
<h:publicationDate/>
<d:modificationdate/>
<h:title/>
</d:prop>
</d:select>
<d:from>
<d:scope>
<d:href>${href}</d:href>
<d:depth>1</d:depth>
</d:scope>
</d:from>
<d:where>
<d:not-is-collection/>
</d:where>
<d:orderby>
<d:order>
<d:prop><h:publicationDate/></d:prop>
<d:ascending/>
</d:order>
</d:orderby>
<!--
<d:limit>
<d:nresults>50</d:nresults>
</d:limit>
-->
</d:basicsearch>
</d:searchrequest> <d:searchrequest xmlns:d="DAV:" xmlns:slide="http://jakarta.apache.org/slide/";
xmlns:h="http://hippo.nl/cms/1.0";>
<d:basicsearch>
<d:select>
<d:prop>
<h:caption/>
<d:displayname/>
<h:index/>
<h:type/>
<h:publicationDate/>
<d:modificationdate/>
<h:title/>
<h:contentDate/>
</d:prop>
</d:select>
<d:from>
<d:scope>
<d:href>${href}</d:href>
<d:depth>3</d:depth>
</d:scope>
</d:from>
<d:where>
<d:and>
<d:not-is-collection/>
<d:gte>
<d:prop><h:contentDate/></d:prop>
<d:literal>${today}</d:literal>
</d:gte>
</d:and>
</d:where>
<d:orderby>
<d:order>
<d:prop><h:contentDate/></d:prop>
<d:ascending/>
</d:order>
</d:orderby>
<d:limit>
<d:nresults>${limit}</d:nresults>
</d:limit>
</d:basicsearch>
</d:searchrequest> 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
