Hello,
I would like to express my concerns with the new logging API.
Logging is fundamental in every software system. Therefore, when the
Java platform introduces its own logging API, it should be as good as
possible.
My biggest concern is that once an immature logging API is out, it
might
weaken the Java platform ,due to its huge influence.
For the last four years, I have been implementing with Java large
enterprise systems (e.g. trading, SCM, e-commerce). Two years ago, I
adopted the Log4J logging API (currently under the Apache umbrella,
formerly by IBM). I believe that this API is by far much more mature
than the proposed API. I think that the Java logging API should adopt
the concepts that are implemented in Log4J.
The biggest flaws of the proposed API, and which are better
implemented
in Log4J are:
1. Lack of generality - Log4J can be used in all Java environments,
including application servers (EJB's), servlets, and custom
applications, and is compatible with JDK 1.1 , 1.2 and 1.3.
2. Limited flexibility - the configuration process in Log4J is plain
and
simple (both properties and XML), and allows you to alter almost
every
aspect of logging, in any order.
3. Limited extendibility - one can get all his logging needs by
assembling and extending existing log elements.
4. Poor error handling - log never fails your application (no
RuntimeException).
I ask you to reconsider publishing the API at its current stage. You
might consider using Log4J instead, or if you'd like, implement the
important concepts that are in Log4J.
Respectfully yours,
Guy Nirpaz
Tantian