Glen/Costin
I understand that the cost is LOW (we are using 'static Log' now). I also understand that I've introduced one more level of abstraction.
I understood Axis to be both a frame work and a SOAP solution. My focus is the framework, and integrating that framework into/with other products
On Tue, 2 Jul 2002 [EMAIL PROTECTED] wrote:
> Glen, I understand BUT.. Calling LogFactory.getLog
> - forces a hashtable lookup on every call to obtain the correct LogFactory
> implementation (key is classloader)...
That's why you would call LogFactory.getLog() only once, at init time.
Most proj
Glen, I understand BUT.. Calling LogFactory.getLog
- forces a hashtable lookup on every call to obtain the correct LogFactory implementation (key is classloader)...
- doesn't guarentee that the LogFactory implementation found is the same one used by the rest of Axis (context class loaders, etc)
B
Rick:
I'm sorry, but I'm still -1 on getLog(). I think it simply obfuscates what is already
a clean and extensible interface.
I'm fine with a generic way of getting properties from "the universe", but I see no
need for getLog().
--Glen
> -Original Message-
> From: [EMAIL PROTECTED]
-
> From: Russell Butek [mailto:[EMAIL PROTECTED]]
> Sent: Monday, April 01, 2002 3:41 PM
> To: [EMAIL PROTECTED]
> Subject: Re: cvs commit: xml-axis/java/test/wsdl/multithread
> MultithreadTestCase.java
>
>
> Glen, you say you have a low # of multithread threads that
>
Glen, you say you have a low # of multithread threads that succeed. How
many? I get:
[junit] Had 328 successes (of a possible 400)
and thereabouts (though I've also gotten as few as 40; don't know why).
There WILL be a certain # of failures because the test is just throwing
lots of calls si
