I put the log4j.jar in orion's lib directory, and use -Dlog4j.configuration=file:path/to/log4j.properties to initialize log4j. I'm pretty happy with this approach. I control logging on a server-wide basis, so I can use the same ear file for both testing and deployment.
Jeff Schnitzer [EMAIL PROTECTED] > -----Original Message----- > From: Alex Paransky [mailto:[EMAIL PROTECTED]] > Sent: Friday, January 18, 2002 5:35 PM > To: Orion-Interest > Subject: FW: Integrating LOG4J into Orion... > > One more time, the last one did not show up.... > > -----Original Message----- > From: Alex Paransky [mailto:[EMAIL PROTECTED]] > Sent: Thursday, January 17, 2002 11:09 AM > To: Orion-Interest > Subject: Integrating LOG4J into Orion... > > > I have a full EJB/JSP application running with Orion. Is there a > preferred > method of initializing LOG4J in this situation? > > Looking at the LOG4J documentation, they mention using a startup servlet > to > do the initialization. I am concerned as to how this would work with the > CLASSLOADER hierarchy. If I initialize my LOG4J at the servlet (WEB) > layer, > will the EJB's be able to see the initialized LOG4J or will they attempt > to > re-initialize due to the different classloader? > > Thanks. > -AP_ >
