jakarta-cactus-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vincent Massol" <vmas...@octo.com>
Subject Re: [proposal] Cactus Logging strategy for Cactus 1.3
Date Tue, 20 Nov 2001 20:37:18 GMT


----- Original Message -----
From: <alvins@dsl.ab.ca>
To: "Cactus Users List" <cactus-user@jakarta.apache.org>; "Vincent Massol"
<vmassol@octo.com>
Sent: Monday, November 19, 2001 7:59 PM
Subject: Re: [proposal] Cactus Logging strategy for Cactus 1.3


> Hi,
>
>   I like the suggestions so far.
>

good :)

>   What is the expected initialization sequence if the user creates a
> log4j Category instance?
>
>   Will the Cactus initializer always run before the log4j initializer?
> After?  Order dependent?
>
>   A well defined ordering is nice to have.
>

The order is the following :
1/ Initialization is always performed by Cactus first
2/ The application to test should not initialise log4j. If it does, log4j
will be reinitialized with the application parameters. It means that the
cactus appenders won't be defined and you'll see a warning on the console
saying that log4j cannot find the appender for category org.apache.cactus.

Note: Solving 2/ is not possible with Log4j 1.1.x (apart from using
Hierarchy but then your application under test needs to be coded in a
certain way, which won't work for us). However, it is possible with Log4j
1.2 (in alpha or beta) by using the notion of Repository.

>
> Alvin.

-Vincent


--
To unsubscribe, e-mail:   <mailto:cactus-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:cactus-user-help@jakarta.apache.org>


Mime
View raw message