Enable automatic JSP reloading

 

+

Search Tips   |   Advanced Search

 

To view changes to the theme and skins JSPs without restarting the portal server, we can force the application server to automatically check for new versions of JSPs. While this is ideal for development and testing purposes, automatic JSP reloading should be disabled in a production environment because of performance issues.

To enable automatic JSP reloading:

  1. Open the file...

    was_profile_root/config/cells/cell/applications/wps.ear/deployments/wps/wps.war/WEB-INF/ibm-web-ext.xmi

  2. Find the following entry in this file: 

    <webappext:WebAppExtension xmi:version="2.0" 
                           xmlns:xmi="http://www.omg.org/XMI" 
                           xmlns:webappext="webappext.xmi" 
                           xmlns:webapplication="webapplication.xmi" 
                           xmlns:commonext="commonext.xmi" 
                           xmlns:common="common.xmi" 
                           xmi:id="IBM _WPS_Ext" 
                           reloadInterval="3" 
                           reloadingEnabled="false" 
                           fileServingEnabled="true" 
                           directoryBrowsingEnabled="false" 
                           serveServletsByClassnameEnabled="false" 
                           preCompileJSPs="false">

  3. Change the value for reloadingEnabled to true.

  4. Save the file.

  5. Restart the portal server.

After completing these steps, JSPs are automatically reloaded when they are changed. However, to view changes to a JSP that is included by another (parent) JSP, also change the parent JSP to indicate that it must be reloaded by the server.

 

Related information