<br><font size=2 face="Verdana">That sounds perfect! I noticed that the
current svn content only includes the getInstance() methods. Do you have
any plans on implementing the other deprecated methods? See http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/Category.html
for reference.</font>
<br>
<br><font size=2 face="Verdana">M. Hansen</font>
<br>
<br><font size=2><tt>user-bounces@slf4j.org wrote on 19-08-2008 21:44:29:<br>
<br>
> <br>
> As similar request has been made by Michael Rumpf in bug 95.<br>
> <br>
> http://bugzilla.slf4j.org/show_bug.cgi?id=95<br>
> <br>
> The getInstance() methods were added recently in SVN. You can expect
these <br>
> methods to be part of the next release.<br>
> <br>
> HTH,<br>
> <br>
> M. Hansen wrote:<br>
> > Hi,<br>
> > <br>
> > We have decided to use JDK1.4 logging and we have some legacy
applications<br>
> > that uses log4j. Our idea is to use SLF4J to bridge calls to
log4jto jdk1.4<br>
> > through SLF4J. However, we do not have the source code for some
of our<br>
> > legacy applications and some use deprecated functionality from
log4j. More<br>
> > precisely we have run into a problem where some code invokes<br>
> > Category.getInstance(java.lang.String). This method is deprecated
in log4j<br>
> > but still part of the API (<br>
> > http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/Category.html).<br>
> > The log4j bridge does not include deprecated functionality. Why
is this? If<br>
> > the bridge is targeted for use in legacy applications it is most
likely the<br>
> > code will make use of an older log4j where the methods were not
marked as<br>
> > deprecated.<br>
> > <br>
> > Regards<br>
> > M. Hansen<br>
> <br>
> -- <br>
> Ceki Gülcü<br>
> <br>
> QOS.ch is looking to hire talented developers located in<br>
> Switzerland. Please contact ceki@qos.ch for details.<br>
> _______________________________________________<br>
> user mailing list<br>
> user@slf4j.org<br>
> http://www.slf4j.org/mailman/listinfo/user<br>
</tt></font>