gwt-log - Runtime logging for your Google Web Toolkit projects.

by Fred Sauer

Key Features:

• Client logging code is compiled out and introduces zero-overhead^* due to GWT compiler dead code elimination when log_level=OFF
• Serializable classes (domain objects, DTOs, POJOs, etc.) can utilize the same logging code on client and server via inclusion of a single, common, gwt-log jar on both tiers
• Remote logging option, which sends copies of all client log messages to the server
• Optional deobfuscated JavaScript stack traces on the client, providing you with pretty Java-esk stack traces in Production Mode, even when your application has been compiled with -style OBF[USCATED]
• Server side logging for mobile devices such as Android devices and the iPhone
• Server side logging automatically detects Apache log4j, falling back to JDK 1.4 logging
• Seven out-of-the-box log levels (TRACE, DEBUG, INFO, WARN, ERROR, FATAL, OFF)
• Log level can be controlled via ?log_level=... URL parameter, GWT <meta name="gwt:property" content="log_level=..."> tag in your HTML, or in your *.gwt.xml module file
• Wide variety of context sensitive log destinations: draggable popup DIV, Firebug / console.log(), GWT.log(), System.err()/System.out(), remote (server) logging
• Ability to independently control compile time and runtime log levels
• Out-of-the-box UncaughtExceptionHandler via Log.setUncaughtExceptionHandler()
• Catch and log non-GWT JavaScript exceptions on the page (in supported browsers)
• Works seamlessly with Google App Engine for both client and server side logging
• Logging categories

^{* Unless your logging parameters are determined by the GWT compiler to have side effects}