Hello everyone, Having spent some time trying to understand why when I deploy a new version of my JSP, it was not recompiled, I observe that in fact a new version is taken into account only if the modification timestamp of the new JSP (Linux Environment) is newer than the modification timestamp of the class generated for the JSP in the work directory.
If I change the modification timestamp of the JSP directly into the webapps directory with a command like: touch-m-t 1104071423.16 BonjourResult.jsp and set it to a newer value, it works very well. The big problem is that this method of detection does not work for a rollback... You can of course do the cleaning at the work directory level but it is not at all adequate in terms of performance since it will force the recompilation of all the JSPs to the application. Under Websphere I do not observe this behavior, if the timestamp is different (and not only older) then the JSP is recompiled. I'm pretty surprised by this difference, can you confirm it to me ? Is there any way to reload the JSP as soon as the modification timestamp changes, and not only when it is older than the modification timestamp of the .class file previouly generated ? Thank you in advance.
