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=38676>. 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=38676 ------- Additional Comments From [EMAIL PROTECTED] 2006-02-19 21:13 ------- I think you are right. There are two things: 1) When JasperLoader loads a class it checks if the class has already been loaded by the super URLClassLoader. But in our case a new instance of JasperLoader is used every time JspCompilationContext.load() is being called. So the TagFile class is really loaded every time load is called for it. For Tomcat 5.5 this changed, the JasperLoader is being reused, so the problem is hidden by that. 2) For Servlets the attribute reload of JspServletWrapper is used to determine, if the servlet should be reloaded. ctxt.load() is being called in the JspServletWrapper methods: - getServlet() if reload is true - loadTagFile() if reload is true - getDependants() if isTagFile and reload are true reload is set to true: - as default in JspServletWrapper - in JspServletWrapper.setServletClassLastModifiedTime() after updating the mtime to true - in JspCompilationContext.compile() if isPackagedTagFile or jspCompiler.isOutDated() reload is set to false: - in JspServletWrapper.getServlet() after loading to false So I think, yes, reload has to be set to false in loadTagFile(). -- 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]
