I suppose that servlet runner checks the timestamp of the main servlet .class file
(or the servlet archive)
so if you change the date of that file (recompile it) EVERY servlet
runner SHOULD RELOAD the servlet
DK bean or servlet descends from another class you have created. However, if
DK you
Macromedia?
thanks
Bill
[EMAIL PROTECTED]
Duffey Kevin
kduffey@BUYMEDIATo: [EMAIL PROTECTED]
.COMcc:
Sent by: A Subject: Re: Dynamic class reloading
and JRun
Hi,
I have the same painful process. Infact, this is the reason I use Orion App
Server (www.orionserver.com) during development! Orion has the ability to
reload servlets and javabeans. However, it TOO needs to be restarted IF the
bean or servlet descends from another class you have created.
-Original Message-
From: A mailing list about Java Server Pages specification
and reference
[mailto:[EMAIL PROTECTED]]On Behalf Of Heske Chris
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
Yep. Resin 1.1 (http://www.caucho.com), will reload when any servlet/bean/class
changes. That's assuming, of course, that the class is in WEB-INF/classes or
WEB-INF/lib. There's nothing that any servlet engine can do if you change
something in the global classpath.
-- Scott
Heske Chris
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
