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=16509>. 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=16509 Incorrect usage of context ClassLoader for static field initialization [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From [EMAIL PROTECTED] 2003-02-17 22:43 ------- Thanks for the report; I think your analysis is correct. The only thing I changed in your patch was to enable fallback processing in the both places: it's possible that, at some point in the future, the serializer for example might be deployed in a different jar than ObjectFactory; therefore, it isn't impossible to imagine that different classloaders might be returned from SerializerFactory.getClassLoader() and ObjectFactory.getClassLoader(). Therefore it seems reasonable for an attempt at a fallback to be made, if for some reason the initial attempt does not succeed. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
