RE: Small Bug + Fix in LogBrokerMonitor.java

In some of our other projects, we have run into cases where foobar.getClass().getClassLoader() returns null. I wonder if this has anything to do with the fact that we are setting the bootclasspath when we lauch the Java VM. I would assume that whoever makes the fix in the official Log4J codeline

DO NOT REPLY [Bug 10140] - chainsaw can not view xml in a log message

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_b

Re: Small Bug + Fix in LogBrokerMonitor.java

OK, now I'm confused [sarcastic gasps from the rest of the list]. How did the original code ever work? LogBrokerMonitor is part of the lf5 contribution, and all the image files are in org/apache/log4j/lf5/viewer/images. So, are ClassLoaders able to locate resources even when the URL is inco