On Aug 28, 2007, at 7:35 PM, Karan Malhi wrote:
I dont even think they can change log levels. We used the logic that
- if conf is present - use logging.properties
- if conf is present - logging.properties is absent- install
logging.properties and use it
- if conf is absent, assume embedded and use
embedded.logging.properties which is available in the openejb-core.jar
.
- if embedded.logging.properties is not found in openejb-core.jar then
rely on the log4j.configuration system property
So, if openejb is embedded within GERONIMO, no matter what log levels
they set in the var/logs directory, those settings should never take
effect.
I think what we can do though is that Geronimo can set the
log4j.configuration system property in the
o.a.g.openejb.OpenEjbSystemGBean and we can then do the following:
- if conf is absent, assume embedded, look for log4j.configuration
system property. if log4j.configuration property is set, then use it,
if it is absent then use embedded.logging.properties
Do you think I am on the right track and does the above makes any
sense?
Do you know if there is a way to check to see if the "OpenEJB" log4j
category has been explicitly configured? If so we could skip the
whole business and assume whatever embedded environment we're in has
taken responsibility for logging.
-David
