I messed around w/ this problem for a few hours, and
since it was so painful I can't recall 100% exactly what fixed it. It might be
that log4j wasn't loaded for that app [class not found caught & null
returned, null giving class cast...], or that a log4j was not configured right
[odd, I thought it failed safe, but seems true], or that you needed
commons-logging.properties with
org.apache.commons.logging.LogFactory=org.apache.commons.logging.impl.Log4jFactory
or that a bad commons-logging.jar was shipped in the webapp/WEB-INF/lib
directory. My guess would be one of the former, but I pretty much tried
all.
Why it happens in one direction I do not know, if it is
one server [not two] but I've seen some folk here talk about TC classloader
issues that go over my head. If two --- environment.
regards
Adam
-----Original
Message-----
From: Mike Brown [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 21, 2002 3:42 PM To: [EMAIL PROTECTED] Subject: ClassCastException in commons logging
|
- ClassCastException in commons logging Mike Brown