I am considering a design where a thread calls a long running query, uses
the results to generate a JSP and then write the new JSP over the old JSP.
Tomcat would then notice the update, recompile the JSP and display the new
query results. The query/rewrite would happen once every 10 minutes.
This is by far a better way to do things than putting an applet on the
page. Tomcat does in fact throw an IOException if the other end of the
socket has closed. If you need to detect the user backing out of
something, just send a byte down ever now and then to see if the connection
is still
Servlet reloading works fine under Tomcat, however I've been bitten where
the servlet re-loaded OK, but a class my servlet depends on changed but was
not reloaded.
For example, if ServletA uses StaticServiceB. I can reload ServletA all
day long, but changes to StaticServiceB wont be picked up
I used to have trouble with this, but now I just use System.err.println();
System.err behaves as you would expect by default.
(Assuming you're not already using err for something else.)
Jason
--
Warning : The
