Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cocoon.apache.org
Message-ID: <027e01c42e24$66f466d0$1a724052@CARROUF>
From: "Eddy Fras" <efras@softeam.fr>
To: <users@cocoon.apache.org>
References: <001e01c42e12$73c33b00$1a724052@CARROUF> <40914569.4000507@gmx.de>
 <026c01c42e20$3b043860$1a724052@CARROUF> <40915AFF.3090107@gmx.de>
Subject: Re: JSP Generator question
Date: Thu, 29 Apr 2004 21:58:54 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

> On 29.04.2004 21:29, Eddy Fras wrote:
>
> >>>Is it possible to avoid a JSP page to be reloaded and recompiled using
> >
> > the
> >
> >>>JSPGenerator in Cocoon when the file has been changed on filesystem ?
> >>
> >>Don't you mean "until the file has been changed on filesystem"?
> >
> >
> > No, I'd like to completely avoid having the JSPGenerator checking if the
jsp
> > file has changed.
> > So, even if the file has been changed on filesystem, I would like to
have
> > the jsp not recompiled.
>
> Hmm, ok, but what exactly is the use case?

I realize it is quite strange but it is in a performance test environment
and we don't want to take jsp file modifications into account.

> > So I could write my own JSPGenerator, just adding the
> > CacheableProcessingComponent interface implementation and that would be
> > enough ?
>
> Yes, just extend the existing one. But unlike the FileGenerator in
> getValidity() you must not return the validity of the inputsource (which
> is normally the lastmodified value), but the "always valid validity":
>
http://cvs.apache.org/viewcvs.cgi/avalon-excalibur/sourceresolve/src/java/org/apache/excalibur/source/impl/validity/NOPValidity.java

I'll try that, thanks a lot,

Eddy


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org