Greetings,
I'd like to propose that the Log4J logging toolkit hard-wired into AXIS
today be replaced with the Jakarta common logging interface
(jakarta-commons/logging).
With support of the AXIS community, I will assume responsibility for making
the required changes to the existing code base.
**Justification**
1. Choice: replace dependency on a particular (albeit quite nice) logging
toolkit with a "pluggable" interface.
2. Consistency of Open Source middleware logging: I consider it a primary
concern that by using various open-source toolkits (AXIS amoung them) I may
be forced into supporting/prividing MULTIPLE logging toolkits at the
back-end (Log4J, Avalon, J2EE 1.4). Yes, I can "pick" a primary logger and
use Adapters to route all others "through" it... but the a common logging
interface and one logger is clearly preferable. Remember that applications
will have to be shipped with JAR files representing every logger.
3. Integration with System logging: Using Log4J today, if I am to
integrate the AXIS middleware into a larger system, my integration point is
the Log4J Appender. This is really a variant of point (2). By wrapping
the in-house system logger into the Log4J appender I unnecessarily "double"
my logging time. In addition, it is not clear how much "extra" work Log4J
performs (object rendering) that may be unnecessary in the context of the
in-house system logger/logging.
4. Consistency with logging configuration. The system integrator must be
familiar with all logging toolkit configuration/control schemes. If an
end-user has to get their hands into multiple config/control schemes...
Points (2) and (3) are very important to our team, as we attempt to
use/integrate AXIS and other open-source community projects into our
solutions.
**Impact**
1. Minimal impact on "use" of logger in AXIS. Since Log4J is "still
there", configuration and control of logging will remain the same for AXIS
as-is (note that Jakarta common logger interface defaults to a Log4J
implementation, if found).
2. Minimal change to AXIS code (import statements, use of factory).
Coding style (create a Log, equivalent to a Log4J Category) is similar,
basic concepts remain the same. I have not done an "exhaustive" search on
the use of Log4J in the AXIS code base, so commentary here would be
appreciated.
Thanks,
<ras>
*******************************************
Richard A. Sitze [EMAIL PROTECTED]
