Hello,
I need to log in different files based on thread group.
So I created my own RepositorySelector which supports exactly this
scenario but in order for this to work I cannot have
static Logger logger = Logger.getLogger("X");
because the last instance that is created is setting the logger o
Java House skrev den 05-07-2008 16:27:
How bad is it, to NOT use static logger;
By having the logger variable static it means it is only initialized
once when the class is loaded where as a non-static logger is
initialized each time you create a new object from the class. If you do
this a
O/H Thorbjørn Ravn Andersen έγραψε:
Java House skrev den 05-07-2008 16:27:
How bad is it, to NOT use static logger;
By having the logger variable static it means it is only initialized
once when the class is loaded where as a non-static logger is
initialized each time you create a new objec
Java House skrev den 05-07-2008 18:10:
O/H Thorbjørn Ravn Andersen έγραψε:
Java House skrev den 05-07-2008 16:27:
How bad is it, to NOT use static logger;
By having the logger variable static it means it is only initialized
once when the class is loaded where as a non-static logger is
ini
On Jul 5, 2008, at 1:27 AM, Scott Deboy wrote:
When does the previous version of Chainsaw get taken out of log4j jar?
Earlier this week I responded to questions about how to configure
Chainsaw to use receivers. It turns out he was using the old
version of Chainsaw.
Would be nice to avoi
Great suggestion!!!
I think this will keep me happy and satisfy library's recomendations.
Thanks
O/H Thorbjørn Ravn Andersen έγραψε:
Java House skrev den 05-07-2008 18:10:
O/H Thorbjørn Ravn Andersen έγραψε:
Java House skrev den 05-07-2008 16:27:
How bad is it, to NOT use static logger;
I don't have a problem with deprecating for one release, but I don't think we
need to keep them in there until log4j 2 - we aren't talking about an API that
folks are coding against and the bits never change, so folks interested in
using the original Chainsaw can just use an old version of log4j
