axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "marc fleury" <marc.fle...@jboss.org>
Subject RE: Issue: remove calls to BasicConfigurator in Options.java and Axis Engine.java
Date Tue, 02 Oct 2001 14:07:41 GMT
|Maybe the answer is to put a default log4j.properties at the top level of
|the axis.jar file, which we can reasonably expect will be on the classpath.
|The problem then becomes getting your own log4j.properties 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

marcf

|sure you can guarantee in app server environments.
|
|Thoughts?  I'd love to get this nailed.
|
|--Glen
|
|> -----Original Message-----
|> From: Mark Roder [mailto:mroder@wamnet.com]
|> Sent: Monday, October 01, 2001 10:48 PM
|> To: 'axis-dev@xml.apache.org'
|> Subject: Issue: remove calls to BasicConfigurator in Options.java and
|> Axis Engine.java
|>
|>
|>
|> Options.java 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 log4j.properties 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
|> http://jakarta.apache.org/log4j/docs/manual.html#defaultInit
|>
|> Later
|>
|> Mark
|>


Mime
View raw message