The Jaxer beta is shipped with the server side exception and error handling configured for a development environment.

What this means is that messages generated server-side will be propagated to the browser for simpler debugging and faster development. If the error occurred before the final processing of the page, the HTML returned to the browser may well contain server-only code. To prevent such code and detailed error messages to ever be seen by users in a production environment, we highly recommend you change the Config.DISPLAY_ERRORS option before going live with your application.

The following code will generate an error, that with the default configuration is displayed in the browser as shown below:

If you set the Config option Config.DISPLAY_ERRORS in local_jaxer/config.js to be false, server-side errors cause the output page to be completely replaced by one containing the following message:

The error data is still logged to the Jaxer log file so no failure information is lost.