On Tue, 11 Oct 2011 13:12:08 -0300, Bryan Lewis
wrote:
But the lower-level classes, not part of Tapestry's domain, don't reload.
For example, I've got business logic in my domain objects, in a
lower-level "model.jar". I've tried running with that jar exploded and
updating the
.class file
Yes, I'm sure that's what he meant. Version 5.3 will turn off live class
reloading in production, which is why he's saying you'll have to run in
development mode.
To clarify my original question (now that it's a dead horse)... I wasn't
worried about reloading of the pages and other top-tier clas
Sorry, but the words "*turns off*" below should be "*turns on*", right?
Development mode will turn on live class reloading, right?
CMIIW...
On Tue, Oct 11, 2011 at 2:25 AM, Howard Lewis Ship wrote:
> That would be a very silly idea, and not necessary. If you deploy an
> exploded WAR (with appli
Also in your container you can set it up for debugging - i.e. attach to port
number X, for debugging with eclipse.
If that's what your intention was as well.
On 11/10/2011, at 6:25 AM, Howard Lewis Ship wrote:
> That would be a very silly idea, and not necessary. If you deploy an
> exploded WAR
That would be a very silly idea, and not necessary. If you deploy an
exploded WAR (with application class files and resources on the file
system, not inside a WAR file) you can get hot swapping (but you'll
need to run in development mode in 5.3, which turns off live class
reloading in production).
Eclipse is not a web container, so you're not running Tapestry in Eclipse
anyway.
On Mon, Oct 10, 2011 at 22:42, Bryan Lewis wrote:
> This might be a silly idea, but I'll ask it anyway... Would it be bad to
> run a Tapestry application inside Eclipse on a production server? The
> objective wou
