> -----Original Message----- > From: Vincent Massol [mailto:[EMAIL PROTECTED]] > Sent: 13 December 2002 07:40 > To: 'Cactus Users List' > Cc: [EMAIL PROTECTED] > Subject: FW: Problems with Cactus and commons-logging > > > > -----Original Message----- > > From: Jerome G. Fillon [mailto:[EMAIL PROTECTED]] > > Sent: 13 December 2002 06:14 > > To: [EMAIL PROTECTED] > > Subject: RE: Problems with Cactus and commons-logging > > > > Indeed it is a classLoader problem. > > > > I have the same problem with strutsTest. > > > > I was able to run my test with the junit.textui.TestRunner and not > with > > awtui or swingui. > > > > The apache code is breaking when trying to validate that a class > (Logger > > JDK1.4 or any other logger) implements the Log Interface... which it > > does when you look at the code. > > If you check the apache code, you will find that the code is quite > > messing around with classloaders to keep the instance of the logger in > > the right classloader... > > > > The work around when running with junit is: > > > > 1) use the textui > > > > 2) unchecked the 'reload classes every run' checkbox > > when using the gui...
or 3) exclude the classes from the reloading class loader. See http://jakarta.apache.org//cactus/faq.html#faq8 (and http://junit.sourceforge.net/doc/faq/faq.htm#runners_1). > > > > > > I'm not registered to the cactus mailing list, so i replied you > directly. > > > > -- > > Jerome > -Vincent -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
