You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Eddy Fras <ef...@softeam.fr> on 2004/04/29 19:50:24 UTC
JSP Generator question
Hi,
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 ?
The Tomcat settings seem to be ignored but perhaps it is normal because the
JSPEngine object is created by Cocoon.
Any ideas ?
Thanks a lot,
Eddy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: JSP Generator question
Posted by Eddy Fras <ef...@softeam.fr>.
> 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
Re: JSP Generator question
Posted by Joerg Heinicke <jo...@gmx.de>.
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?
> 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
Joerg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: JSP Generator question
Posted by Eddy Fras <ef...@softeam.fr>.
> On 29.04.2004 19:50, 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.
> > The Tomcat settings seem to be ignored but perhaps it is normal because
the
> > JSPEngine object is created by Cocoon.
> > Any ideas ?
>
> Both the JSPGenerator and JSPReader could implement
> CacheableProcessingComponent, what they don't do at the moment. It would
> be the same as in the FileGenerator.
So I could write my own JSPGenerator, just adding the
CacheableProcessingComponent interface implementation and that would be
enough ?
Thanks Joerg,
Eddy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: JSP Generator question
Posted by Joerg Heinicke <jo...@gmx.de>.
On 29.04.2004 19:50, 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"?
> The Tomcat settings seem to be ignored but perhaps it is normal because the
> JSPEngine object is created by Cocoon.
> Any ideas ?
Both the JSPGenerator and JSPReader could implement
CacheableProcessingComponent, what they don't do at the moment. It would
be the same as in the FileGenerator.
Is it what you want?
Joerg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org