In the current project I have used Log4J through Apache Commons Logging in
a Spring-based application - this is the common configuration in Spring
components.
Because of business requirements on bigger flexibility of logging
configuration I have to switch to the Log4J successor - LogBack.
I included SLF4J and jcl-over-slf4j to my POM and did not change any line
in my Java code.
Afterwords I just replaced the log4j.xml with logback.xml, and finished -
each library / framework included in the application happily logs using
logback - even if they originally have not been designed for logback.
Summary: Apache commons logging API is a de-facto standard in the
open-source community. If we would go in different direction, there is a
chance to go in conflicts with other OSS frameworks / libraries. The
implementation of this API may be replaced by any other new logging
product, that has to support this API - because of the current de-facto
standard position.
tomi
On Oct 13, 2009 9:37pm, Arthur Ryman <[email protected]> wrote:
I vote for alignment with Axis.
Arthur Ryman, IBM DE
Chief Architect, Rational Project and Portfolio Management
Office: 905-413-3077, Cell: 416-939-5063
Assistant: Nancy Barnes, 905-413-4182
Sagara Gunathunga [email protected]>
10/12/2009 07:48 AM
Please respond to
[email protected]
To
[email protected]
cc
Subject
[VOTE] Vote for Woden Logging Strategy
Hi all,
I have implemented Logging Strategy for Woden based on SLF4J but later
Andreas provided some comments on Axis2-dev list, that's leads me in
to rethink about Woden Logging strategy. I'm requesting all of you
to
vote for following options and I encourage to read the comments[1]
before voting it contains enough details to take a decision .
1.) SLF4J API
2.) Commons-logging API
3.) Any other API ( If so please mention)
[1] - https://issues.apache.org/jira/browse/WODEN-71
Thanks ,
--
Sagara Gunathunga
Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
