I didn't update all copies... I didn't realize I had to as I thought the version local to the webapp would be all that matters (is this by any chance the much-discussed autodiscovery/classloader issue rearing its ugly head??)
If I am not mistaken, by default Websphere uses the parent-first class loader delegation model which goes to explain the behavior you are observing.
I also did not update commons-logging-api.jar as I don't have that installed with my app, only commons-logging.jar is present.
Although not generally truem, in this particular case, parent-first delegation implies that the copy of JCL in your web-app will be ignored.
I'll go hunt down all copies now and update them, see what happens...
-- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com
-- Ceki G�lc�
The complete log4j manual: http://www.qos.ch/log4j/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
