axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "marc fleury" <>
Subject RE: Issue: remove calls to BasicConfigurator in and Axis
Date Tue, 02 Oct 2001 16:22:19 GMT

I see you are in charge here... good talking to you christoph

I'll tar.gz myself, peace!


|-----Original Message-----
|From: Jung , Dr. Christoph []
|Sent: Tuesday, October 02, 2001 10:27 AM
|To: ''
|Subject: AW: Issue: remove calls to BasicConfigurator in
|and Axis
|I think what Glen is supposing is to remove the static log4j initialization
|code in AxisEngine altogether and to put a default into
|axis.jar instead (hence to use the log4j.Category-builtin initialization
|I would be happy with this, since, e.g., JBoss initializes log4j before
|deploying axis.jar, it even does that in a super-classloader such that IMHO
|log4j.Category would not even find the the axis.jar!
|-----Urspr√ľngliche Nachricht-----
|Von: marc fleury []
|Gesendet: Dienstag, 2. Oktober 2001 16:08
|Betreff: RE: Issue: remove calls to BasicConfigurator in
|and Axis
||Maybe the answer is to put a default at the top level of
||the axis.jar file, which we can reasonably expect will be on the
||The problem then becomes getting your own to
|override that
||one requires making sure it shows up first on the classpath, which I'm not
|For god's sake not the classpath, the context cl maybe
||sure you can guarantee in app server environments.
||Thoughts?  I'd love to get this nailed.
||> -----Original Message-----
||> From: Mark Roder []
||> Sent: Monday, October 01, 2001 10:48 PM
||> To: ''
||> Subject: Issue: remove calls to BasicConfigurator in and
||> Axis
||> and AxisEngine have the following code segment:
||>     static {
||>         BasicConfigurator.configure();
||>         Category.getRoot().setPriority(Priority.FATAL);
||>     }
||> This segment should be removed.  It strongarms the log4j setup and
||> applications can not change the behavior.
||> I am trying to use axis in a client application talking to an
||> existing soap
||> service.  I am using the file in the
||> classpath to setup
||> log4j in the default/lazy method.  I was not getting any of my logging
||> output because axis did the above calls.
||> More information on log4j's default initialization procedure
||> how to setup
||> log4j can be found at
||> Later
||> Mark

View raw message