On 7/24/07, Pedro Herrera <[EMAIL PROTECTED]> wrote:
Caused by: org.apache.commons.logging.LogConfigurationException:
User-specified log class 'org.apache.commons.logging.im
pl.Log4JLogger' cannot be found or is not useable.
at
org.apache.commons.logging.impl.LogFactoryImpl.discoverLogImplementation(
LogFactoryImpl.java:798)
at
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(
LogFactoryImpl.java:601)
at
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(
LogFactoryImpl.java:333)
at
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(
LogFactoryImpl.java:307)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java
:645)
at
org.apache.tiles.web.util.TilesDecorationFilter.<clinit>(
TilesDecorationFilter.java:79)
... 144 more
There it is. Do we have an incorrectly configured (or missing) Log4j Jar
file somewhere or a log4j Jar file in the wrong Classloader?
Greg