I run into problems using log4j_1.2.6 with dbforms. See
DbFormTagTEI.java, line 27-31. So lets see what log4j-doc is warning:
-- This class has been deprecated and replaced by the Logger subclass.
-- It will be kept around to preserve backward compatibility until mid 2003.
Maybe with 1.2.6 it was 2002 and not 2003.
-- Logger is a subclass of Category, i.e. it extends Category. In other
words, a
-- logger is a category. Thus, all operations that can be performed on
-- a category can be performed on a logger. Whenever log4j is asked to
produce a
-- Category object, it will instead produce a Logger object. However,
methods
-- that previously accepted category objects still continue to accept
category objects.
Not with 1.2.6!
-- For example, the following are all legal and will work as expected.
-- // Deprecated form:
-- Category cat = Category.getInstance("foo.bar")
Does not work with dbforms.
-- // Preferred form for retrieving loggers:
-- Logger logger = Logger.getLogger("foo.bar")
--
-- The first form is deprecated and should be avoided. There is
absolutely no need for
-- new client code to use or refer to the Category class. Whenever
possible, please avoid
-- referring to it or using it. "
We have
static Category logCat = Category.getInstance(DbFormTagTEI.class.getName());
in dbforms.
Maybe next release should be a "Logger"?
--- Yves
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
DbForms Mailing List
http://www.wap-force.net/dbforms
