An answer to this question/problem is very important to my project group so
please take time to read and understand it. Thanks. I struggled with
posting this to a JBOSS group but decided it was more of an issue with the
use of Log4J and not so much how JBOSS was using it.
I am using JBOSS
Hello James,
The functionality you are looking for is to be able to log within
unique logger repositories using a custom logger repository selector.
I have implemented such a selector (and a servlet context listener
which configures log4j to use it at app/server startup) which keys
logger
The problem w/ jBoss is that they 'get there first'.. in that they use
log4j for their own internal logging log4j.jar exists in the Containers
CLASSPATH and the first time an internal logging statement is hit log4j
initializes itself w/ the log4j.xml configuration file located (by default)
Thanks Don. I think what you describe is happening. I will search the
forums further.
So, what was your solution? It sounds like the custom
ContextRepositorySelector did not work for you. I may have misinterpreted
your email.
Thanks,
J.D.
-Original Message-
From: donald larmee
Hi,
I am trying to write my customLogger by extending the
java.util.logging.Logger class.
I want to know is this the right approach ,the way I am doing.
class TSPPXMLLogger extends Logger {
private static TSPPXMLLogger logger = null;
public TSPPXMLLogger(String name,String localization){
