Question about Log4j and ObjectRepositoryAssembler
"Christian Cryder" <[email protected]>
| Newsgroups | gmane.comp.java.enhydra.barracuda.general |
|---|---|
| Message-ID | <[email protected]> |
Hey Jake, Here's a question for you about Log4j and ObjectRepositoryAssembler. Basically, everything seems to be working fine for the most part in regards to logging - I am running Tomcat directly (not as a service), and calls to various loggers show up in the Tomcat console, which is where I expect to be seeing them. The issue is that I cannot get the logging for ObjectRepositoryAssembler to show up in the console, and I know it used to. What is happening, is that ObjectRepositoryAssembler logging is going to the log files in Tomcat's logs directories. What I _suspect_ happened is that the problem began when we went away from using the Log4j init servlet - in web.xml, that used to be forced to run before the ObjectRepositoryAssembler. Now, when we switched to the Log4j context listener, I am _guessing_ that the ObjectRepositoryAssembler servlet is no longer waiting for the Log4j stuff before it runs...so if the log4j config stuff is not configured, then that would explain why my logging is initially going to the default log file, and then subseqent logging goes where its supposed to according to what's defined in my log4j.properties. At any rate, that's my theory, and I'd like to get your opinion on it. Its easy to test - just run Tomcat directly and see if you can get ObjectRepositoryAssembler logging to show up in the console. Any suggestions or ideas? tia, Christian ---------------------------------------------- Christian Cryder Internet Architect, ATMReports.com Project Chair, BarracudaMVC - http://barracudamvc.org ---------------------------------------------- "Coffee? I could quit anytime, just not today"