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??)
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. 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 On Tue, April 12, 2005 1:59 pm, Ceki G�lc� said: > Frnak, > > Did you make sure to upgrade *all* copies of commons-logging.jar to 1.0.4? > I believe Websphere has its own copy of JCL. Did you make sure also to > upgrade commons-logging-api.jar? > > At 07:49 PM 4/12/2005, Frank W. Zammetti wrote: >>Further info... >> >>I updated JCL to 1.0.4 and removed the >>org.apache.commons.logging.LogFactory file... logging broke again. I put >>the file back, restarted the app, and logging was once again working. >> >>Log4J version is 1.2.8 incidentally, so I was almost up to date with that >>as well (have NOT updated to 1.2.9). >> >>Any ideas? I have no problem believing I don't have the right answer at >>this point, but it does certainly appear to be fixing the problem >> somehow. >> Thanks! >> >>-- >>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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
