Reg.
I remain convinced that the error is due to duplicate log4j.jar setup. Here is a modified log4j version that is designed to give more information on the reasons of the failure. Here it is: http://qos.ch/log4j-1.2.6.jar Can you please try it and report back? At 10:14 23.07.2002 -0300, Reg Sherwood wrote: >Hi, > >Thanks for the response to my problem of the object is not assignable >message. I still have the problem though. From reviewing what Ceki said >I have looked at my classpath for my given application simple application. > >C:\dev\JDK\jdk1.3.1_04\\bin\javaw -classpath >W:\platform\1.0\PDR001\platform\deploy\lib\platform.jar;W:\thirdParty\xerces\xerces1.1.2_bld1\xerces\deploy\lib\xerces.jar;W:\thirdParty\junit\junit3.7_bld1\junit\deploy\lib\junit.jar;C:\TogetherSoft\Together6.0\lib\junit\junit.jar;W:\thirdParty\log4j\log4j1.2.4_bld1\log4j\deploy\lib\log4j.jar > >test.com.foo.platform.services.log.TestLogSuite > >log4j:ERROR A "org.apache.log4j.net.SocketAppender" object is not >assignable to a "org.apache.log4j.Appender" variable. >log4j:ERROR Could not instantiate appender named "A2". >log4j:WARN No appenders could be found for logger (TestLogger). >log4j:WARN Please initialize the log4j system properly. > >The only mention of log4j on this classpath is the one I explicitly >entered... if I remove the log4j.jar from the classpath, then things will >fail to run as Category, etc are not found. I have also checked all of >the other jars in the chance that they included the log4j classes... no >other classes were found. Now, I am using the TogetherSoft IDE for >startng my tests, but that should cause no problem. Is their any way to >look at my system classloader? > >Thanks > >-Reg -- Ceki For complete log4j documentation, please see http://qos.ch/log4jBook.html -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
