Enable automatic JSP reloading

---

To view changes to your theme and skins JSPs without restarting the portal server, you can force the appserver 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.

Follow these steps to enable automatic JSP reloading:

1. Open...

   $WAS_ROOT/config/cells/node/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.

Note that if JSP reloading does not work, go ahead and cycle the portal server to see your changes.

 

See also

1. Layout of the portal page
2. Tags used by the portal JSPs
3. Customizing the portal
4. Create your own theme
5. Create your own skin
6. Lightweight themes and skins
7. Supporting new clients
8. Supporting new markup languages
9. Portal style classes
10. Change company information
11. Change the portal page help
12. Working with portal navigation
13. Using JSTL tags in the portal JSPs