Hello,
While working on the internal log4j logging, it occurred to me that it could be very useful to synthesize log4j's core user interface in its own package. I'd like to call this package Universal Generic Logging Interface or UGLI (pun intended).
The word "universal" stands for applicability in all contexts, including stand alone applications, containers (EJB, Servlet, Nano, Pico, Avalon, whatever) and most importantly in specialized libraries. The word generic stands for very simple, with an absolute separation between the logging interface required to access logging on one hand and configuration of the logging system on the other.
Given the lessons learned from past experience, in particular wrt extreme simplicity and generality, it is expected that UGLI will be quickly adopted by many developers. However, even if that does not happen and developers chose to ignore UGLI, log4j itself will benefit from the conceptual clarity it brings to the table.
Note that UGLI will be strictly an addition. Thus, developers could continue to use the existing log4j API as is. Alternatively, they would be able to switch to UGLI if they chose to do so. Thus, UGLI is not expected to impact backward compatibility of existing log4j deployments.
I am CCing [EMAIL PROTECTED], avalon-dev and commons-dev to elicit input for this endeavor. Actual code to follow.
Cheerio,
-- Ceki Gülcü
For log4j documentation consider "The complete log4j manual"
ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
