Updated JSP Files Copied to Deployed Application Does not get recompiled in Oracle Containers for J2EE 10g
(Doc ID 989583.1)
Last updated on MARCH 01, 2019
Applies to:Oracle Containers for J2EE - Version 10.1.2.3.0 to 10.1.3.5.0 [Release AS10gR2 to AS10gR3]
Information in this document applies to any platform.
In OC4J 10g, after placing an updated JSP file to a previously deployed application path and accessing it<oracle_home>, the updated JSP page is not loaded, but the old JSP page is.
Restarting OPMN and even restarting Windows do not solve the problem: old JSP page is loaded instead of the updated one.
<oracle_home>Even though JSP container properties have been configured to recompile JSP (main_mode has been set to recompile), when there is change, the modified date of old JSP files is newer than the updated (new) JSP. If the JSP of modified date earlier than the current deployed one is placed, no such problem occurs.
It seem like the JSP runtime dispatcher is looking for a JSP file that has a timestamp greater than the timestamp for the corresponding .class file.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document