Using Log4j for Webdsl log messages

Currently, log messages are now printed to the console on most places by using an ordinary call to System.XXX.println(…)Most messages don’t contain information like date / time and application name. In production environments with multiple applications running, this missing information hinders the debugging of failures (with emphasis on the application name that is missing in the messages).

Hibernate log messages are already exposed through the log4j system.

Let’s change the logging to use Log4j so we can control how log messages are exposed. Furthermore, the hibernate log message pattern must be adapted to include the app name.