Engine View

Figure 9.5. Engine View

The engine view shows information about the running application engine, as well as some details from the application specification.

Under Operations are two buttons: the first restarts the application. The second (when enabled [4]) resets the application, which forces a reload of all component specifications and HTML templates. This is useful during development, since it allows for incremental development without stopping and restarting the servlet container.

Below the operations is a binary dump of the application engine. This is useful when developing to see how large the serialized state is, and perhaps gleam how it might be trimmed.

Further below (and not visible in the screen shot above), is a dump of the request context. This is that vast amount of data also displayed when an unexpected exception is thrown.



[4] By default, the reset service (used by the reset button) is disabled. To enable it, set the JVM system property com.primix.tapestry.enable-reset-service to true. The service is disabled since it is too tempting a target for a denial of service attack.