Ok, just as a clarification :) (It took me a while to find this out myself...)
If development mode is turned off, the jsp is compiled once - and never checked again; even removing the generated class file or removing the jsp file itself has no effect! So turning this off in development makes no sense at all :) I even doubt that this is very usefull for production in the Sling context. If development mode is turned on, jsp files are checked for recompilation every 4 seconds - this value can be changed through configuration. So I turned development mode back on and clarified the properties in the metatype description a little bit :) As a final node, consider this recompilation check if you're doing performance tests :) You definitly don't want to hit a recheck phase during your performance test.... Regards Carsten Carsten Ziegeler wrote: > Felix Meschberger wrote: >> Hi, >> >> This is most probably caused by a recent change in the default value for >> the JSP "development" mode flag: Previously the default value was >> "true", that is on each access to a JSP script, the last modification >> time has been checked. Now, the default value is false and hence the >> last modification time of the script is only checked every 4 seconds (by >> default). >> >> Now, our integration tests replace JSP scripts but since the replacement >> and call happens within 4 seconds before the last call, the old contents >> is still used and hence the tests fail. >> >> I am currently investigating what to do. >> > It seems there is a bug in the jsp script handler - as soon as > development mode is off > it seems to not check anymore at all. At least some quick tests did show > this behaviour. > > Carsten > > -- Carsten Ziegeler [email protected]
