Configuring a server for EGL Web debugging

Before you can debug EGL Web applications, you must configure the server for EGL debugging. You need to do this configuration step only once per server. If you use Tomcat, make sure that you request EGL debugging support at the time you define the new server to EGL.

EGL Debug is the default debugging mode. If you want to debug generated Java™ code rather than the EGL JSF handler, see "Debugging Java code" later in this topic.

To configure a server for EGL debugging, do as follows:

  1. In the Debug perspective, find or open the Server view (Window > Show View > Other > Server > Servers). The Status column of the display says "Debugging" when the server is running in EGL debug mode.
  2. If Status column does not report "Debugging," and the server is not running, right click the server name and choose Debug from the pop-up menu. If the server is running, right-click the server name and click Restart > Debug.
  3. To take the server out of EGL debug mode, right-click the server name and choose Restart > Start.

Debugging Java code

EGL assumes that you want the server to debug EGL JSF Handler parts. If you want to debug generated Java code instead, you must set the egl.jsfhandler.debug system property to FALSE. Do this by passing the property as a VM argument to the server. Methods for doing this depend on which server you are running.

On Apache Tomcat, edit the VM arguments section of the launch configuration (Run > Debug), as in the following figure:

Add -Degl.jsfhandler.debug=false to the top of the list of VM arguments on the Tomcat v5.5 Server launch configuration page

Restart the server for the property to take effect.


Feedback