I need to correct this point:
>
> Now, I think that is happening because struts is using
> commons-digester to read its xml config files, and commons-digester
> includes log4j logging.
>
commons-digester actually uses commons-logging, not log4j.
So, what can I do to find out more how the digest
Allright, the deeper I dig, the more confused I get.
I think there is a bug here, bug I still can't pinpoint how it happens.
Let's say I'm deploying 2 web applications - both use struts, and
therefor have dependencies on commons-digester.
App A starts up. A includes a log4j jar file. As A star
>
> Yes. I manage the log4j configuration myself when my webapp loads -
> from a props file - I'm not using any of log4j's auto configure /
> discovery stuff.
>
Tomcat uses commons-logging for its logging needs. Apache commons
logging does decide what logging implementation to use at the time
whe
On Jan 25, 2008 9:28 PM, Konstantin Kolinko <[EMAIL PROTECTED]> wrote:
> What exactly tomcat, log4j versions are you using?
Tomcat 5.5.23
Log4j 1.2.15
> Do those warnings affect the rest of your application?
No, but my customers notice them and file issues
> Is you
> configuration read a
What exactly tomcat, log4j versions are you using?
It may be a classloader issue. Some of them are occasionally found and fixed.
That looks like commons-logging resorts to use log4j for the Digester
class (instead of java logging aka juli for the server classes), but
cannot find configuration.
This seems to be a fairly common problem, but doesn't appear to have a
common solution. Any help appriciated...
When I launch a webapp, which includes log4j, I get the following warning:
log4j:WARN No appenders could be found for logger
(org.apache.commons.digester.Digester.sax).
log4j:WARN Plea
