DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=33143>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=33143 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[EMAIL PROTECTED] ------- Additional Comments From [EMAIL PROTECTED] 2005-02-05 22:44 ------- I would suggest switching to Log4j 1.3 or the UGLI API ( http://logging.apache.org/log4j/docs/ugli.html ), of which there are implementations for Log4j, JDK1.4 logging, simple system.out logging, and NOP. You decide which implementation by providing it in the classpath and never change the API you reference. Kind of like commons-logging, but without the brittleness of the discovery system. Anyway, if you use Log4j as the implementation (directly or via UGLI-Log4j), you can use a repository selector ( http://www.qos.ch/logging/sc.jsp ) which will effectively separate container logging from application logging using a single instance of Log4j (in common/lib). Actually, you can share logging by giving two apps the same logger repository name to use. Read the Javadoc for more info... http://cvs.apache.org/viewcvs.cgi/logging-log4j/src/java/org/apache/log4j/selector/ContextJNDISelector.java?rev=1.18&view=markup Jake -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
