However, going through the process of pushing an updated banner.html file into the webapps/myapp directory and reloading the application results in the *prior* version of banner.html being used vs. what's sitting right there in webapps/myapp...even after reloading the application using TC Manager. I'm more confused than ever as to why the new .html file isn't being used, especially now that it's dynamically loaded (yes?) with jsp:include vs. compile-time statically include with <%@ include> (even though the latter also makes no sense why the current html wouldn't have been picked up at compile-time either).
I'm using straight Tomcat/Coyote vs. Apache and connector by the way.
At 12/20/2002 12:51 PM, you wrote:
Mark, Sounds like you are using a <%@ include file="file.html"%> style include. This is a static, compile-time include. That means that Tomcat is probably compiling the html file in along with the jsp. The only way to refresh this would be to delete the compiled jsp files in the Work directory.I might suggest that you instead use a dynamic runtime include. For instance, <jsp:include page="file.html"/> This should work as you want. Ian. -----Original Message----- From: Mark [mailto:[EMAIL PROTECTED]] Sent: Friday, December 20, 2002 12:50 PM To: [EMAIL PROTECTED] Subject: JSP not using latest version of included file My app has several JSPs that include an html file (ie. <%@ include file="banner.html" %>) that displays the app's version number. banner.html gets updated every now and then with a new version number via Ant and pushed to the Tomcat webapps/myapp directory along with the JSPs (forced overwrite using Ant copy task). The app is then reloaded w/i Ant via the Catalina reload task. Everything works except the newly compiled JSP isn't including the new html file. It's somehow picking up the prior version. Given a JSP 'login.jsp', the login_jsp.java and login_jsp.class (in the TC ../work/standalone/localhost/myapp directory) both have new timestamps which indicates they were regenerated after the JSPs and html were pushed into place. If I manually delete those generated files forcing another JSP recompile, it *still* won't pick up the new html. If I delete the files (again), stop/start the application in the TC manager, then the newly generated login_jsp.java suddenly includes the new version of the html. It's as if the JSP compiler is using a cached version of the old .html file until I stop the application. I want to display the new included html w/o having to start/stop the app or Tomcat. Can someone explain what's going on? Thanks -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
