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.

Submitted by Elmer van Chastelet on 26 October 2012 at 16:43

On 26 October 2012 at 16:44 Elmer van Chastelet tagged 1.3.0

On 26 October 2012 at 16:44 Elmer van Chastelet tagged @elmer

On 26 October 2012 at 17:31 Elmer van Chastelet commented:

Added in r5450

Webdsl log messages use a different log4j appender, which can be found and adapted in tpl_log4j.properties.

How to log?

Use the static methods from org.webdsl.logging.Logger eg. org.webdsl.logging.Logger.info("this is an informative message")


On 26 October 2012 at 17:31 Elmer van Chastelet closed this issue.

Log in to post comments