it would probably increase chance of this having done if it was in JIRA.
or is it already in?
alek
[EMAIL PROTECTED] wrote:
True :-)
We're having the same sort of trouble, so, it would be nice to get either
rid of commons-logging (to start a flame war here ;-) or have a chaoice NOT
to compile it....
Cheers
-----Original Message-----
From: Priest, Mark [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 02, 2005 3:59 PM
To: '[email protected]'
Subject: RE: Commons logging and Axis (feature request??)
Commons logging is already a wrapper for some other logging
system. It seems a bit much to provide a wrapper on top of
commons logging. Personally, I have had nothing but trouble
with commons logging in Axis and in every other project where
I've used it.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 02, 2005 8:34 AM
To: [email protected]; [email protected]
Subject: Commons logging and Axis (feature request??)
Hi,
would it be possible to modify the logging framework, so that
the commons-logging Log class isn't used anymore throughout
the entire axis distribution, but only in -say- the
org.apache.axis.compontents.logging.Log
class? So you get a more loosely coupled logging framework,
instead of a lock-in. In other words, use an interface
components.logging.Log and an implementation that might (or
not) use commons-logging..... In this way one can build Axis
without commons-logging. This is a requirement if you want to
use JBoss (3.2.5/6), it fails at the moment when using
commons-logging and scoped deployment.
Greetings,
Rutger Lubbers
--
The best way to predict the future is to invent it - Alan Kay
