JavaServer Pages (JSP) files refresh changed from V4.0 to V5.0
 Technote (troubleshooting)
 
Problem(Abstract)
When a JavaServer Pages (JSP) file is updated in WebSphere® Application Server V4.0, the changes are apparent immediately. However, in V5.0 the update is not immediately apparent. What has changed?
 
Resolving the problem
In V4.0, the JSP refresh and the servlet refresh are handled differently:
  • Servlets are refreshed according to the reload interval in the IBM extensions
  • JSP files are refreshed automatically when updated, based on a new time stamp or size change.

In V5.0, the JSP refresh was changed to provide consistent behavior. Since JSPs are compiled servlets, the refresh is now consistent. Both JSPs and servlets are now refreshed based on the reload interval setting in the Web application.

You can modify this behavior using the Application Assembly Tool (AAT) or the administrative console using the Applications Configuration page.
In the WAS 5.0x Administration Console go to the application and modify the "Reload Interval" under "General Properties" for that application. In the AAT go to that application and highlight the web module. Under the "IBM Extensions" tab, modify the "Reload Interval:".

In both cases, Reloading enabled must be checked into IBM extensions for the reloading value to become active.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Servlet Engine/Web Container
Operating system(s): Windows
Software version: 5.0
Software edition:
Reference #: 1105590
IBM Group: Software Group
Modified date: Mar 27, 2004