<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><blockquote type="cite"><tt></tt></blockquote><span class="sender">Ceki wrote:</span><br><blockquote type="cite"><tt>In the existing logging paradigm, you would need to change the level of the
</tt><tt>logging statement by editing the java class containing the given logging
</tt><tt>statement and recompile, repackage and redeploy. Your approach may be a little
</tt><tt>more convenient (only one file needs to edited and compiled even if multiple
</tt><tt>levels needs to be changed). Are there are other advantages?</tt></blockquote></div><div><br></div><div>When we want to change the log level and don't want to redeploy and repackage,</div><div>we'll use way changing log level by ResourceBundle. </div><div>Our operation is to add property file to system class path. </div><div>It don't need recompiling and repackaging. </div><div><br></div><div>ResourceBundle is higher order of precedence than Annotation about resolving log level and log message,</div><div>so we can overwrite log level and log message by ResourceBundle.</div><div>Annotation is for developent time with IDE support.</div><div>Property file is for operation time with no recompiling and no repackaging.</div><div>They are different use cases.</div><div><br></div><div>And Message id management is trouble-filled,so this feature reduces it ,IMO.</div><div><br></div></body></html>