Typically, a change to a class that is referenced in a JSP (or
servlet) requires you to restart the JRun service in order to flush
the "stale" class and reload the new class. This is a painful
process for developers sharing a common JRun development environment.
JRun does automatically recompile and reload the servlet if there is
a change to the JSP page but does not reload any of the referenced
classes.
Do any of the competing JSP/Servlet engines support auto-reloading of
classes (beans) based on a change to the underlying class file
without having to restart the JSP engine?
Is there an elegant way to force JRun to reload classes referenced by
a servlet without restarting the engine?
Cheers,
Chris
This message contains confidential information and is intended only
for the individual named. If you are not the named addressee you
should not disseminate, distribute or copy this e-mail. Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.
E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses. The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission. If
verification is required please request a hard-copy version. This
message is provided for informational purposes and should not be
construed as a solicitation or offer to buy or sell any securities or
related financial instruments.
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
