Enable automatic JSP reloading

Overview

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.

Enable automatic JSP reloading

1. Edit...
   PROFILE_HOME/config/cells/cell_name/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.

Parent topic:

Customize the portal

Related concepts

Portal style classes
Work with portal navigation
Use JSTL tags in the portal JSPs
User and group management

Related tasks

Creating a new theme
Import a theme
Deploy the theme
Creating a new skin
Supporting new clients
Supporting new markup languages
Changing banner text

Related reference

Use the color palette in themes
Performance guidelines for themes and skins

Related information

Changing the page help

---