Mailing-List: contact axis-user-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-user@xml.apache.org
Subject: Re: commons-logging issue (maybe JUnit-related)
To: axis-user@xml.apache.org
Message-ID: <OFE031E339.C44E5AC3-ON48256C83.0007DFDC@erggroup.com>
From: "Steve Kinsman" <SKinsman@erggroup.com>
Date: Mon, 2 Dec 2002 09:33:54 +0800
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii


The solution to this is hinted at in the JUnit documentation, and is
easy to implement.  The problem arises because JUnit uses multiple class
loaders across test cases.  However it has a list of packages it knows
NOT to reload all the time - and you can add to this list.
Copy junit\runner\excluded.properties from junit.jar (e.g.
foo\junit\runner\excluded.properties), and place your copy earlier in
the classpath than junit.jar.  (e.g. classpath should have "foo" before
junit.jar).  Now add the following to your exclude.properties:

#
# This one is needed to stop exceptions in apache logging (& other areas
in Axis too!)
# due to reloading by classloader for each test case
#
excluded.6=org.apache.*

I hope this helps!

Steve Kinsman


                    Mitch Gitman                                                                                                          
                    <mgitman@usa.        To:     axis-user@xml.apache.org                                                                 
                    net>                 cc:                                                                                              
                                         Subject:     Re: commons-logging issue (maybe JUnit-related)                                     
                    30/11/2002                                                                                                            
                    04:08                                                                                                                 
                    Please                                                                                                                
                    respond to                                                                                                            
                    axis-user                                                                                                             
                                                                                                                                          
                                                                                                                                          
Sure enough, this problem does not arise when running my Axis client
directly. So where's the conflict with JUnit? The JUnit archive doesn't
define these classes.

At 11:45 29.11.02 -0800, you wrote:
>I'm trying to run some JUnit tests on an Axis client. My client class'
>constructor calls the default constructor for
>org.apache.axis.client.Service. This causes an exception to crop up:
>java.lang.ExceptionInInitializerError
>at org.apache.axis.client.Service.<init>(Service.java:108)
>...
>Caused by: org.apache.commons.logging.LogConfigurationException: ...
>org.apache.commons.logging.impl.Jdk14Logger does not implement Log
>         at
>
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:555)

>...
>
>Now, Jdk14Logger does implement Log; both are in commons-logging.jar.
At
>first, I thought this was a simple classloading issue, that somehow an
>inconsistent version of the class or interface was being picked up. But

>after moving common-logging.jar to the head of my classpath list for
>invoking JUnit, I still got the error. And anyway, I don't see
Jdk14Logger
>or Log elsewhere in the classpath.
>
>I suspect this issue has something to do with JUnit, although I haven't
a
>technical reason. Just, "Jdk14Logger does not implement Log" has made
its
>way to the Cactus (JUnit for webapps) mailing list. Next, I'm going to
try
>running my Axis client directly rather than through JUnit.
>