Return-Path: Delivered-To: apmail-xml-axis-dev-archive@xml.apache.org Received: (qmail 95076 invoked by uid 500); 2 Oct 2001 14:06:05 -0000 Mailing-List: contact axis-dev-help@xml.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@xml.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-dev@xml.apache.org Received: (qmail 95058 invoked from network); 2 Oct 2001 14:06:04 -0000 From: "marc fleury" To: Subject: RE: Issue: remove calls to BasicConfigurator in Options.java and Axis Engine.java Date: Tue, 2 Oct 2001 10:07:41 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal In-Reply-To: <4F47DCFADC8DD5118D2B00508B952D9645ADE0@salsa.allaire.com> X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N |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 |>