Disabling hot code replacement doesn't mean your web app reloads
instantly, it means it *never reloads*. The classloader loads the .class
file as it existed the first time a class was references and hangs onto that
version of the .class until the JVM cycles. That's why your annotation
changes don't work; they're part of the .class file.
You can, of course, change your .html or .page files if you have
tapestry's cache off and see *those* changes instantly, but without a reload
(either a manual cycle or a tomcat hot replace), your still running the old
bytecode. It's sort of like changing a running unix binary out from under
it. The OS has a copy of the binary in memory so any existing process keeps
running the old version until you cycle the process, even if the one on disk
changes.
--- Pat
> -----Original Message-----
> From: Norbert Sándor [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, January 18, 2006 7:48 AM
> To: Tapestry users
> Subject: Re: First page display slowdown in v 4.0
>
> Disabling reloading of the webapp did not help?
>
> When I use hot code replacement I always disable reloading, so my webapp
> is
> updated instantly. (Not always, eg. annotation changes are applied only on
> restart for some reason... :(
>
> BR,
> Norbi
<snip>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
