On Sep 20, 2007, at 9:25 AM, Karan Malhi wrote:
I think the best option is to set the system property openejb.logger.external to true and totally control log4j configuration from tomcat. This is what Geronimo does right now. The openejb.logger.external property is used specifically to configure logging if openejb is intended to be embedded within external containers. In my opinion that should be the standard way of doing it regardless of whichever external software is trying to embed OpenEJB. So, tomcat could define its own tomcat.logging.properties file which could be used to configure logging .
Tomcat uses java.util.Logging and doesn't do any Log4j config, so if we don't do it there'll be no logging.
In my opinion, we should remove the hack from the Logger.
Resolving the paths relative to openejb.base isn't a tomcat specific thing. If someone starts openejb from any directory but openejb.base then the logging files won't get created because the paths will resolve to user.dir unless we resolve them for log4j.
-David
