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 ?
>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?
After more investigation, the use case is the following :
To improve performance in Tomcat, it is possible to disable the checking system for JSP file modification.
I would like to do exactly the same with the JSPGenerator (and also the JSPReader) in Cocoon.
So, I don't know if I really need to cache the result of the generator or if there is better way to just avoid Cocoon checking if the JSP file has been changed.
Thanks,
Eddy
>> 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
