I
thought we were using Apache Commons Logging which is a thin veneer
over
any variety of logging apis.
From:
"George Stanchev" <Gstanchev@xxxxxxxxxx>
To:
"Higgins (Trust Framework) Project developer discussions"
<higgins-dev@xxxxxxxxxxx>
Date:
05/29/2008 12:16 PM
Subject: RE: [higgins-dev] Log4J vs JSR47
loggers in Higgins' IdAS code
SLF4J (
http://www.slf4j.org/)
already implements a logging facade that
Higgins can use that can
abstract JSR47, log4j or logback logging. Its
using a permisive MIT
license.
Just a suggestion.
From:
higgins-dev-bounces@xxxxxxxxxxx [
mailto:
higgins-dev-bounces@xxxxxxxxxxx] On Behalf Of Paul
Trevithick
Sent: Thursday, May 29, 2008 9:48 AM
To: 'Higgins (Trust
Framework) Project developer discussions'
Subject: RE: [higgins-dev]
Log4J vs JSR47 loggers in Higgins' IdAS
code
Prakash,
Assuming for the moment that Higgins folks
agree with swapping JSR47 for
Log4J, are willing to work on and
contribute a patch along these lines?
-Paul
From:
higgins-dev-bounces@xxxxxxxxxxx [
mailto:
higgins-dev-bounces@xxxxxxxxxxx] On Behalf Of Prakash C
Mallick
Sent: Thursday, May 29, 2008 7:52 AM
To:
higgins-dev@xxxxxxxxxxxSubject: [higgins-dev] Log4J
vs JSR47 loggers in Higgins' IdAS code
Hi All,
I found that higgins' IdAS uses log4j for lgging . As
IdAS APIs
consumer will be from different organizations, they will have
their only
guide lines for selecting a logging framework , this sort of
direct usage
of logging calls from Log4J will have the following
limitations.
1. Say an existing software uses JSR47
logging framework and they plan
to use IdAS API in one of their component. They
will niether prefer
to maintain two logging
frameworks simultaneously to use IdAS API
nor will
they will prefer to move to log4j if they plan to use IdAS
API. Admining two logging mechanism in one software will be
not a
good idea and also if the software is having
a large code base , its
not possible to move from
one existing logging frame work to Log4J.
2. Loggers as
choosen based on performance, internationalization
flexibility , better features and so on , but
this way the user will
have no choice but stick to
log4j even if its a good logging toolkit.
3. Many
roganizations will have their own logging framework or they will
have some standard to use a specific logging
framework . So using
IdAS API based on Log4J may
not be possible for them.
Similarly there can be many such limitation
which needs to be identified.
To over come such issues, Is it
possible to implement logging using one of
the following ways or any
other ways which can help in avoiding such issues
mentioned
above.
1. Replace Log4J with JSR47 (preferrable as
in many areas JSR47 is the
preferred logger compared to
Log4J)
2. Write a wrapper logging framework which can be
either configured for
Log4J and JSR47
Thanks and
Regards,
Prakash
---------------------------------------------------------------------------------------------------
Advisory
Software Engineer,
Tivoli Security Products
India Software Lab, IBM
Software Group
Ozone, SP Infocity, Saswad Road, Fursungi, Pune 412
308
Ph: +91-20-2690-1013
e-mail:
prakash.mallick@xxxxxxxxxx---------------------------------------------------------------------------------------------------
**********************************************************************
This
email and any files transmitted with it are confidential and
intended
solely for the use of the individual or entity to whom they
are addressed.
Any unauthorized review, use, disclosure or distribution
is prohibited. If
you are not the intended recipient, please contact
the sender by reply
e-mail and destroy all copies of the original
message.
**********************************************************************
_______________________________________________
higgins-dev
mailing list
higgins-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/higgins-dev
_______________________________________________
higgins-dev
mailing list
higgins-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/higgins-dev