In a nutshell, the server side of WaveMaker applications are debugged like any other Java application. We use logging, log4j more specifically, and Eclipse, InteliJ IDEA, or otherwise our preferred tool to attach to the server with a debugger. Most often, we use Java Platform Debugger Architecture (JPDA) to establish the connection between debugger and debugee.
Logging in WaveMaker uses the Apache log4j 1.2, http://logging.apache.org/log4j/1.2/, for logging. We have seen that we generate log entries from Java and how log levels are set using the log4j.properties file in the /src folder. The log levels are in order of increasing verbosity: FATAL, ERROR, WARN, INFO, and DEBUG.
A common mistake made when reading WaveMaker log files occurs when the project fails to start due to some XML error, such as in a bean configuration. The project will most likely fail to start with a BeanCreationException error. However, the last error logged is from testrunstart, which only knows that that...