Details
-
Type:
New Feature
-
Status: Closed
-
Priority:
Major
-
Resolution: Duplicate
-
Affects Version/s: 1.7DR#3
-
Fix Version/s: 2.0-Alpha3
-
Component/s: Framework, ICE-Components
-
Labels:None
-
Environment:ICEfaces
Description
ICEfaces currently uses commons-logging, introducing a dependency on commons-logging.jar. Java provides a built-in logging API, java.util.logging, that should be evaluated as a replacement.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
We are examining our logging strategy for ICEfaces 2.
Show
Deryk Sinotte
added a comment - We are examining our logging strategy for ICEfaces 2.
We're revisiting our logging strategy as part of development of ICEfaces 2.0. At this point, we're leaning to using java.util.logging to avoid extra dependencies on 3rd party libraries.
Show
Deryk Sinotte
added a comment - We're revisiting our logging strategy as part of development of ICEfaces 2.0. At this point, we're leaning to using java.util.logging to avoid extra dependencies on 3rd party libraries.
This can be a religious issue, but I think that a library should not use a concrete logging framework. If Icefaces uses java util logging, then users of icefaces who also use log4j (like me) will have to find a way to bridge jul to log4j.
Other libraries like hibernate (commons logging) all apache libraries (commons logging) and jetty (slf4j) use an abstract logger, which does not force the user to use a particular logging implementation.