Hello Struts, Now I try to make Jakarta-Log4j based Log4jService - service for ServiceManager - to make this service available for all Struts environment for common logging mechanism. But great part of Log4j is based on static methods and vars...
My main idea is to write some kind of Adapter for various logging implementations - LogService. ServiceManager, ActionServlet and Action classes can use it to perform logging operations. Default implementation for LogService is Log4jService - ServiceManager instantiates it at init moment, if no one logger class is specified in config. By this scheme end developer can write his own LogService implementation (for example, JSR47 specification based) and all stuff will use it as standart logger. So logger instance must hide all details from Action classes. Concrete logger must work with some object to perform logging operations - create at init moment, configure it and use as internal resource. Static methods and vars in Log4j is not so good for such model.... Can anybody suppose any idea about logging mechanism or about some logging implementation without static stuff? -- Best regards, Oleg mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>