DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16481>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16481 Incorrect usage of context ClassLoader for static field initialization ------- Additional Comments From [EMAIL PROTECTED] 2003-02-06 05:53 ------- I am very opposed to this proposed change as it is. It needs to be carefully evaluated in light of the class loading strategies used by various J2EE containers such as Tomcat (for servlets, anyway), WebSphere, and WebLogic. The proposed change prevents different web applications from having different copies of Encodings and OutputProperties and I think that might be desirable. I need to look at the classloading extension for Eclipse and understand how that works and why Eclipse can't set the thread context classloader, which is the way it should be handled, at my first impression.
