Debug Wicket AJAX in the CMS

The Wicket AJAX debug window is available only in brXM version 14.x. This feature is not supported in version 15.0 and later. For more information, see Wicket Ajax debug window in Upgrade 14 to 15: Upgrade to Wicket 9.

To inspect the CMS AJAX framework behavior, start the CMS in Wicket development mode. Use the following command line option to enable this mode:

mvn -Pcargo.run -Dcargo.jvm.args='-Dwicket.configuration=development'

When Tomcat starts, you should see the following log message:

[INFO] [talledLocalContainer] ********************************************************************
[INFO] [talledLocalContainer] *** WARNING: Wicket is running in DEVELOPMENT mode.              ***
[INFO] [talledLocalContainer] ***                               ^^^^^^^^^^^                    ***
[INFO] [talledLocalContainer] *** Do NOT deploy to your live server(s) without changing this.  ***
[INFO] [talledLocalContainer] *** See Application#getConfigurationType() for more information. ***
[INFO] [talledLocalContainer] ********************************************************************

After enabling development mode, the CMS user interface appears unchanged. However, the following changes occur internally:

The HTML markup includes comments that mark the start and end of each Wicket component.
Wicket logs warnings if components contain non-serializable fields. Non-serializable fields prevent Wicket from serializing sessions.
When a Wicket AJAX call results in an error, a Wicket AJAX debug button appears in the bottom-right corner of the page. Select this button to open a logger window that displays AJAX responses from the server.
In several areas of the CMS, such as Experience manager and CKEditor, JavaScript files are no longer concatenated. Instead, all JavaScript sources are included separately to simplify debugging.