Rife, Brandon wrote:
During development when I modify templates and classes and hot-deploy
those files to my app server I find that I have to restart the app
server anyway because of, I assume, Tapestry's caching. That's great
behavior for a production environment but kind of a pain for
development. Is there a Tapestry switch I can flip to turn off caching?
Well, there's an option you can pass the vm that may help:
-Dorg.apache.tapestry.disable-caching=true
Try it and see if it makes a difference. I've managed to get it all to
work so I can develop from Eclipse without having to restart when
templates/pages or java class files change (unless hotcode replacement
fails, but then I just press restart without redeploying).
--John
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
