Development/Java & J2EE/Websphere/Portal/Enable jsp recompile for Websphere Portal pages 1 Enable jsp recompile for Websphere Portal pages: set reloadingEnabled="true" in:\\ {code} <was_root>/config/cells/<hostname>/applications/wps.ear/deployments/wps/wps.war/WEB-INF/ibm-web-ext.xmi {code} Note this is the where the deployed code live. On a live server this can sometimes be overridden again form wps.war, so it can be changed in {code} <was_root>/AppServer/installedApps/<hostname>/wps.ear/wps.war/WEB-INF/ibm-web-ext.xmi {code} More detailed: {code} Enabling automatic JSP reloading To view changes to your theme and skins JSPs without restarting the portal server, you 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. Follow these steps to enable automatic JSP reloading: 1. Open the file was_profile_root/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, you must also change the parent JSP to indicate that it must be reloaded by the server. {code} 2006-08-23 11:39:38.0 2006-08-23 11:39:38.0