I actually tried: org.apache.* .. ok, turns out I did not place the property file
in
the right
location.
Richard
Scott Stirling wrote:
> Have you tried adding org.apache.commons.logging.* to your excluded.properties in
>JUnit?
>
> Scott Stirling
> Macromedia
>
> -Original Message-
Have you tried adding org.apache.commons.logging.* to your excluded.properties in
JUnit?
Scott Stirling
Macromedia
-Original Message-
From: Richard Emberson
If one uses Junit's TestCaseClassLoader loader - letting one run the
test with its own classloader,
then the logging system th
If one uses Junit's TestCaseClassLoader loader - letting one run the
test with its own classloader,
then the logging system throws an exception:
.java.lang.ClassCastException:
org.apache.commons.logging.impl.LogFactoryImpl
at
org.apache.commons.logging.LogFactory.newFactory(LogFactory.ja
I was on leave, but here's a somewhat belated +1 to your proposal.
Glyn
> If I recall correctly, JCLI didn't exist when we last had
> this discussion,
> and the impression (possibly incorrect) at the time was that Avalon's
> LogKit prereqed the Avalon Framework. In any case, JCLI not
> only doesn't
> prereq any outside framework, it has it as a part of it's design
To: [EMAIL PROTECTED]
@IBMUS cc:
Subject: RE: Interop with Log4j & AXIS
Logging in general
Richard Sitze wrote:
>
> The JCLI is an interface with thin-wrapper implementations of that
> interface for Log4J, Avalon Toolkit, J2EE 1.4 Logging API, a simple
> (System.out) logger, and a NoOp Logger. The "category" notion is handed
> straight through, so if you are using Log4J you loose only
Glen Daniels
<[EMAIL PROTECTED]>
cc:
02/08/2002 11:16 Subject: RE: Interop wi
?
--Glen
> -Original Message-
> From: Richard Sitze [mailto:[EMAIL PROTECTED]]
> Sent: Friday, February 08, 2002 12:00 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Interop with Log4j & AXIS Logging in general
>
>
> Given:
>
> 1. my earlier proposal to repl
Given:
1. my earlier proposal to replace the direct Log4J dependency in AXIS with
the Jakarta Common Logging Interface (defaulting to Log4J),
2. The resounding silence (defaulting to a Yes vote), and
3. The current situation...
I'm moving forward as proposed. This should either correct the
Greetings,
I'd like to propose that the Log4J logging toolkit hard-wired into AXIS
today be replaced with the Jakarta common logging interface
(jakarta-commons/logging).
With support of the AXIS community, I will assume responsibility for making
the required changes to the existing code base.
11 matches
Mail list logo
