Stephen McConnell wrote:
> I'm presuming that the phrase "logging interface required to access > logging" is specifically the client interface against which a logging > message is invoked (as opposed to anything related to how an instance of > that interface is created). Is that correct?
Good question. UGLI will consist mostly of interfaces to be implemented by others, log4j for one.
Given that the UGLI will cater for libraries implemented as POJOs, there is a need to standardize the logger creation mechanism. However, this does not mean that IoC techniques could not be used to inject logger instances into the POJO.
> The second phrase "configuration of the logging system" is somewhat > broader and I wanted to find out if your thinking about the general area > of how plug-in logging targets can be managed in a managed classloader > environment. This subject is currently the major obstacle to the use of > different logging solutions and a common API for loading, deploying and > releasing plug-in target factories would be a big step forward.
Questions regarding configuration of logger contexts are outside the scope of UGLI.
BTW, you can see an initial draft in
http://cvs.apache.org/viewcvs.cgi/logging-log4j/src/java/org/apache/ugli/
-- Ceki G�lc�
For log4j documentation consider "The complete log4j manual"
ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
