>
>
> The common practice (with almost any Java logging framework) is to have
> your loggers as static final fields and using the class name as the logger
> name (some logging frameworks even have static factory methods taking a
> java.lang.Class as "name").
>
> Re. the common practice
GWT provides java.util.logging.Logger but my source code was depending in
apache-commons logging. So I reimplemented apache-commons logging based on
the logging facilities of GWT. The same can be done if your code depends on
log4j or slf4j. You can keep the same packaging structures so you can
On Tuesday, November 8, 2016 at 4:36:20 AM UTC+1, vitrums wrote:
>
> Recently I found, that some log4j-like functionality in my client's code
> could be handy. So with the GWT logging module I can pretty much have a
> shared logging code, which is very convenient to use on both sides. The
>
Recently I found, that some log4j-like functionality in my client's code
could be handy. So with the GWT logging module I can pretty much have a
shared logging code, which is very convenient to use on both sides. The
tutorial is here http://www.gwtproject.org/doc/latest/DevGuideLogging.html
.
