Luis Neves <[EMAIL PROTECTED]> wrote:
Hello all,
I have two simple questions.
1-Is there some way that can force Tapestry to NOT cache
the *.jwc files and the html templates?
Whenever I make changes I have to restart the
web server, this is getting tiresome, I am sure there is a
knob some where that controls this behaviour. I seem to
remember reading something about it in the documentation,
but I can't find that information now.
This is perhaps a bit off-topic, but I suppose that it could be interesting to some people.
Besides disabling caching, as described in the other messages, another possible approach is also to use a servlet container that allows dynamic reload of web applications.
Tomcat is one such container -- it allows you to remove and then redeploy a running web application without a restart through its 'manager' application. Unfortunately, its WebAppClassloader does not provide as full coverage as it should, so in the released versions that feature does not work properly for some applications, including Tapestry-based ones.
I have patched the code here to fix that, and locally we are using this patched version. Combined with a small Ant script, it allows us to build a distribution and redeploy an application in about 4-5 seconds total (the server is not restarted in the process). Needless to say, this is very convenient during development and saves a tremendous amount of time. This approach has an added advantage as well -- it works when you update Java classes, not only jwc files.
I have not yet submitted my changes to Jakarta yet, though I hope to be able to do it soon. Nevertheless, if anyone wants the patch, email me, and I'll send it to you.
All the best,
-mb
P.S. I suppose an alternative to all that would be to use a lightweight servlet container that can be restarted quickly (Jetty?). I have had to work with Tomcat, however, so I do not know what the speed of that approach is.
Do You Yahoo!?
LAUNCH - Your Yahoo! Music Experience
