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=5711>. 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=5711 classloader caching resource files in 4.0 Summary: classloader caching resource files in 4.0 Product: Tomcat 4 Version: 4.0.1 Final Platform: All OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Webapps AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Hi- I have a .properties file that I use for my application configuration that I keep in WEB-INF/classes. I use getClass().getResourceAsStream ("/myfile.properties") from within a bean to load the properties into a static hashtable, and I have a control servlet that can tell the bean to reload the file. This just allows me to edit the properties without having to start and stop the application (which was a more painful process pre-Catalina). Now that I've switched from 3.2.3 to 4.0.1, what I'm seeing is that my changes to the properties file are not being picked up when I reset my bean. I've traced through everything, and determined that my subsequent calls to getResourceAsStream are still opening the original file, even though I've modified and saved it. Its as if the classloader is treating the resource as a class, and it is loading it once and keeping it around, so I need to reload the application to reload the resource. This was not the behavior under 3.x, so my question is, is this proper behavior in 4.x or a bug? If it is proper behavior, is there a workaround? Thanks! -Richard -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
