This is something I can't even consider: this is a production system, not a development one. I can't afford not to use caching of the templates (it would be too slow otherwise).
I need to find a way to discard the cache whenever I need it. Regards, J�r�me. On 5/27/05, Ben Walding <[EMAIL PROTECTED]> wrote: > Take a look at > http://jakarta.apache.org/tapestry/faq.html#faq-N10197-menu (you'll have > to scroll down manually) > > J�r�me BERNARD wrote: > > >Hi, > > > >I have a client that basically wants to be able to change the layout > >of the pages generated by Tapestry. > > > >He is usually working with DreamWeaver using the templating feature so > >that he can easily change all his static pages. > > > >He would like to be able to use those DW templates with Tapestry > >pages. This could be quite easy: DW would generate the templates used > >by Tapestry (for DW it would be regular files generated by its own > >template). But the thing is, my client may change quite frequently the > >templates (about once a week), so I need to find a way to reload the > >templates "on demand" and potentially to have the templates "out of > >the webapp" so that my client can FTP them (otherwise, I'll try to use > >symlinks with an exploded WAR). > > > >Any suggestion on how to do this efficently (restarting the webapp is > >not an option)? > > > >Regards, > >J�r�me. > > > >--------------------------------------------------------------------- > >To unsubscribe, e-mail: [EMAIL PROTECTED] > >For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
