> > Tomcat uses java.util.Logging and doesn't do any Log4j config, so
> > if we don't do it there'll be no logging.
I thought tomcat used to use apache commons logging at one point. So
they switched. Actually I was thinking if we could configure logging
in one of the integration classes written by Dain and not tomcat
itself. But, then we will see tomcat logs go to a different file than
openejb logs (which may be desirable, or maybe not)
>>Resolving the paths relative to openejb.base isn't a tomcat specific
>>thing.
Totally agree with you, that's why I was thinking that we could do
something like
${openejb.base}/logs/openejb.conf instead of the hack (see below, I
think the hack was a good idea actually)> > Tomcat directly uses the org.apache.juli (http://tomcat.apache.org/ > tomcat-6.0-doc/logging.html) for logging, which by default is hard > coded to only use java.util.Logging. For Tomcat embedded mode, I'd > like to be able to swap out our Logger implementation for one that > uses juli so all of our log messages flow into the normal Tomcat stream. > > If someone has time to look at making Logging plugable, I think it > would make embedding OpenEJB into different environments cleaner. I am so glad you asked for it Dain. I was hoping that someone would want it some day. I would definitely like to work on it. Actually , I think the hack by Dain is more of a requirement now if we want pluggable logging ;) Thanks for the logging hack ... err... feature Dain ;) -- Karan Singh Malhi
