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=23406>. 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=23406 <jsp:include> shows partial output after the included file has been modified ------- Additional Comments From [EMAIL PROTECTED] 2003-09-25 11:07 ------- [PURE SPECULATION] You are seeing a race condition. While the file (menu.jsp) is being generated to its destination - a request is made for it. During this sime time, a request is made for the file. The file is read incompletely by the JSP compiler, and the write happens quick enough that all of this occurs in the same second so the JSP engine does not detect a file change. I have seen this on tomcat404. You have 3 workarounds: 1) If its a plain text file, just call it menu.txt. This also saves some overhead of a JSP. 2) Generate the file to a temporary area on the same disk. Then use a file copy from/to local disk. 3) Tweak the jsp to force a compile error of itself if it is not complete. A simple brace <% { %> at the top of the file then closing brace at the bottom should work. It would be nice for Jasper to store the file size and date to perform its checks for situations such as this. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
