hi Boris,<br><br>Can you explain me how a static Logger can create problems at a shared class in a server environment?<br><br>thank you in advance, Kostas<br><br><div><span class="gmail_quote">On 13/06/06, <b class="gmail_sendername">
Boris Unckel</b> <<a href="mailto:boris.unckel.mlg@gmx.net">boris.unckel.mlg@gmx.net</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br><br><br>>-------- Original-Nachricht --------<br>>Datum: Tue, 13 Jun 2006 11:30:47 +0100<br>>Von: Konstantinos Karadamoglou <<a href="mailto:kkarad@googlemail.com">kkarad@googlemail.com</a>><br>> Which is the best practice of declaring Loggers? For instance, should
<br>> they be static, private, final? and why?<br>this depends on the environment:<br>For shared classes in server environments a "private final" is useful.<br>For non-shared classes or non-server environments I recommend a "private static final" declaration.
<br><br>Generally you have less pain without "static" but you have more instances, which may become a problem.<br><br>Regards<br>Boris<br>_______________________________________________<br>user mailing list<br><a href="mailto:user@slf4j.org">
user@slf4j.org</a><br><a href="http://slf4j.org/mailman/listinfo/user">http://slf4j.org/mailman/listinfo/user</a><br></blockquote></div><br>