Ceki wrote:
In the existing logging paradigm, you would need to change the level
of the logging statement by editing the java class containing the
given logging statement and recompile, repackage and redeploy. Your
approach may be a little more convenient (only one file needs to
edited and compiled even if multiple levels needs to be changed).
Are there are other advantages?
When we want to change the log level and don't want to redeploy and
repackage,
we'll use way changing log level by ResourceBundle.
Our operation is to add property file to system class path.
It don't need recompiling and repackaging.
ResourceBundle is higher order of precedence than Annotation about
resolving log level and log message,
so we can overwrite log level and log message by ResourceBundle.
Annotation is for developent time with IDE support.
Property file is for operation time with no recompiling and no
repackaging.
They are different use cases.
And Message id management is trouble-filled,so this feature reduces
it ,IMO.
_______________________________________________
dev mailing list
dev@slf4j.org
http://www.slf4j.org/mailman/listinfo/dev
