First, it's unusual to name your logger after the name of the log file you
expect it to go to. But I guess that's up to you. Your real problem is
probably that you haven't compile your classes with debug info (the java -g
option).
Jake
On Mon, 16 Jun 2008 12:11:37 +0530
"Debarshi Sanyal"
The FQCN is used for determinating the class which issued the log call.
The log framework produces a callstack and searches backwards until it
has found the supplied FQCN. The next entry is then taken for expanding
the %C pattern in the layout.
Normally, if you use the myLogger.debug() (et al.) me
I do not agree to yours "Logs are not for debugging". In heavy loaded
multithreaded applications it could be the only way to debug. The DEBUG
level IS definitively for debugging purpose. In production, I agree, the
level should be INFO or higher.
Heri
> -Original Message-
> From: Julius Da
There might be a problem if you use your own RepositorySelector wich
maintains different Repositories depending on some context (MDC etc.).
Utility classes whose methods can run in different contexts should fetch
the logger each time where it is used.
Heri
> -Original Message-
> From: J
