Hi all,
I didn't find out why I was getting the same date/time value
over and over, but I found a better way to do what I needed.
Instead of calling an XSP that did a SELECT statement,
I just used the DateInputModule in the sitemap.

Regards,
Lars

> -----Original Message-----
> From: Yves Vindevogel [mailto:[EMAIL PROTECTED]
> Sent: Friday, May 07, 2004 4:06 AM
> To: [EMAIL PROTECTED]
> Subject: Re: esql xsp page caching?
> 
> 
> Hi Lars,
> 
> I bumped into the same problem too, but, I found out that it was not 
> Cocoon who was caching.
> My client had a Mickeysoft Isa Server as proxy and even with the meta 
> tags like "pragma no cache", Isa kept caching the URL.
> I found out that it was based on the URL, so when I gave another URL 
> with a dummy parameter in it, it did not cache.
> What I eventually did, was adding the session-id to the URL, so at 
> least between two sessions, the problem was fixed.
> 
> On 06 May 2004, at 23:55, Lars Huttar wrote:
> 
> > Hi all,
> >
> > I have the following simple XSP page:
> >
> > <xsp:page language="java"
> >     xmlns:xsp="http://apache.org/xsp";
> >     xmlns:xsp-request="http://apache.org/xsp/request/2.0";
> >     xmlns:esql="http://apache.org/cocoon/SQL/v2";
> >     xmlns:sil="http://www.sil.org/namespace/cocoon-sql-logicsheet";>
> >
> >   <footer>
> >     <code><xsp-request:get-parameter name="code"/></code>
> >
> >     <sil:query connection="ethnolog">
> >             SELECT to_char(sysdate, 'Dy dd-Mon-yyyy') AS 
> Current_Date,
> >                          to_char(sysdate, 'HH:MM AM') AS 
> Current_Time
> >              FROM Dual
> >     </sil:query>
> >
> >   </footer>
> > </xsp:page>
> >
> >
> > It works as expected, except that once you start running it,
> > it continues to return the same answer for the Current_Time,
> > even 1/2 hour later!
> > Anybody know if this is an XSP/ESQL caching issue, or perhaps
> > an Oracle db issue?


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

Reply via email to