Page History

...

This section describes a method that will be especially useful for testing small changes in JSP files without having to go through a cumbersome reload process. This example will demonstrates configuring the plancreator plugin for tomcat:

1. Modify <GERONIMO_HOME>\var\catalina\conf\web.xml:
   • Set the development parameter to true in the init-param to org.apache.jasper.servlet.JspServlet.
   • Edit (add if doesn't exist) the modificationTestInterval to 0
2. In the webapp that you intend to modify, find the web.xml and remove the servlet and servlet-mapping of the jsp you intend to modify and test.
   For example, for PlanCreator, edit the plancreator-console-tomcat-2.2-SNAPSHOT.car\WEB-INF\web.xml.
3. Restart the server with these settings in place.

...

If you make changes to a Java Server Page (JSP) packaged in an already-deployed application archive in Eclipse, the changes will result in a redeployment of the whole package.
Starting from Geronimo 2.2, you can configure the server with a new option No re-deployment when only JSP files are updated. Thus, GEP will not redeploy the whole package when only .JSP files are changed. This option will only be available when Geronimo server is stopped.
To enable the feature, follow these steps:

1. Stop Geronimo server if it is running;
2. On the Servers view, double click the server to be configured. And select No re-deployment when only JSP files are updated on the result panel; A message window will pop up with instructions.
3. Edit <GERONIMO_HOME>/var/catalina/conf/web.xml file and set the development attribute for JSP pages to true.

   Code Block
   xml xml title excerpt from web.xml
   <servlet> <servlet-name>jsp</servlet-name> <servlet-class>org.apache.jasper.servlet.JspServlet</servlet-class> <init-param> <param-name>development</param-name> <param-value>true</param-value> </init-param> ... </servlet>

4. After all is done, restart the server in Eclipse.