Best Practices: Web Application Development

Disabling Class Reloading During Development

During iterative web application development, WebLogic Server can perform a partial redeployment of changed class files each time a page is loaded in the browser. This partial redeployment can, however, lead to unpredictable behavior depending on how the partial redeploy interacts with the web frameworks that are used by the web application.

This unpredictable behavior can be avoided by either (1) avoiding page refreshes in the browser or (2) by disabling class reloading in the Server's development mode.

To disable class reloading, set the <servlet-reload-check-secs> element in WEB-INF/weblogic.xml to -1 as shown below:

  <wls:container-descriptor>
      <wls:servlet-reload-check-secs>-1</wls:servlet-reload-check-secs>
  </wls:container-descriptor>

When a web application is configured this way, WebLogic Server will not perform a partial redeploy of the web application and will wait for redeployments that are initiated manually via the administration console / command line or via Workshop using the Run > Run As menu.

For more information see Avoiding Unnecessary JSP Recompilation on the dev2dev site.