So they both seem to be the same (???)...
You probably run into a class loader problem. Classes with the same name can still be incompatible if they were loaded by different class loaders (umm, roughly).
Because it is the logkit jar that is causing these ClassCast exceptions, could it be an issue with my logkit.conf?
No. You have to shuffle the jars around further. Unfortunately I'm not a security context wizard, so I can't quite tell you what works. If all else fails, move *all* jars you need into the JDK's lib/endorsed directory.
----- Original Message -----Should have been snipped already.
J.Pietschmann
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
