Mailing-List: contact axis-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@xml.apache.org
Message-ID: 
 <3D2560A1F8CFD21192CA0008C75B87CE0334D79E@inforka4.karlsruhe.infor.de>
From: "Jung , Dr. Christoph" <christoph.jung@infor.de>
To: "'axis-dev@xml.apache.org'" <axis-dev@xml.apache.org>
Subject: Configuring Log4j
Date: Fri, 28 Sep 2001 17:32:22 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello,

I=B4m just integrating the axis-alpha as a regular deployment service =
into
JBoss. I stumbled over the following code in =
org.apache.axis.AxisEngine:

 static {
        BasicConfigurator.configure();
        Category.getRoot().setPriority(Priority.FATAL);
    }

which confuses the whole logging-setup of JBoss after
classloading/instantiating  org.apache.axis.AxisServer=20

Do you require that the AxisEngine.class (and hence your default =
logging
configuration) must be initialised before any application (server) =
using the
package is configuring its logging behaviour?=20

At least in the upcoming JBoss Rabbit-Hole release, we are trying to
bootstrap and hot-deploy nearly every part of the server (including the =
axis
deployer) and this would require a lot of ugly workaround code to =
reinstall
the logging configuration each time.

IMHO, any service package that is a part of a larger applications
(application servers) - and thats what Axis can be with highest value -
cannot and should not decide about the whole logging configuration. =
Hence
the above code, if at all, would be better done, e.g., in the main =
method of
the client applications ...=20

I hope that I could (and will in the near future) contribute some =
valuable
thoughts.=20

BTW, did I say that I really like the Axis approach?=20

CGJ