AbstractSimpleImpl

getMDC

setLevel

If you want to override the level in the configuration file
fixed for this category, you can do it with this method. This
could be usefull for example to switch on all debug logging
when something has gone wrong.

trace

debug

Logs the message m with debug priority. Everything a
non-developer never wants to see, but you do, to * keep track
of what is happening. There can be a lot of them in the code,
so it is important that you well protect them with
`isDebugEnabled's, to minimize overhead.

debug

service

Logs the message m with service priority. An interested system
administrator might want to see these things. For examples all
queries to the database could be logged with `service'
priority. Or if a image is calculated, that could be logged as
a `service'. One would get a fairly good idea what MMBase is
doing if `service' is switched on.

service

info

Logs the message m with info priority. As `service', but
focussed on things system administrators are usually most
interested in, like authorisation issues. For example changes on
the database could be logged, such that one can see in the logs
what happened.

error

fatal

Logs the message m with fatal priority. The progam could not
function any more. Normally, you would throw an exception,
which then will be logged with fatal priority. I've made an
arangement in `Logger' that logs uncatched exceptions with
fatal priority, but nevertheless it's better to always catch
all exceptions in a more regulated way.