I'll be looking into UGLI as well, but I currently code directly to the log4j API. Not that it doesn't have it's own set of issues in a J2EE environment, but my impression is that JCL can be much worse. Here's something else to chew on:

http://www.qos.ch/logging/thinkAgain.jsp

Vic wrote:
That's great about Java.
I am going the other way, from JCL to the new log4j:
http://logging.apache.org/log4j/docs/ugli.html

.V

[EMAIL PROTECTED] wrote:

Today I find myself converting an existing webapp from using Log4J directly to using JCL instead. As per the JCL User's Guide, I'm creating a private static Log variable in all my classes, Struts Actions included.

My question is, why is this OK? Static variables in Actions are a Bad Thing, that's a ell-known fact, but why is a Log instance an exception to this rule?

Is it only a bad thing to have static members that might be updated? Is that the difference here? Thanks all!

-- Kris Schneider <mailto:[EMAIL PROTECTED]> D.O.Tech <http://www.dotech.com/>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to