Digging through Tapestry code, I've seen that the reset service do actually call the ResetEventCoordinator identified by service point "tapestry.ResetEventCoordinator". Wouldn't it be simpler to call directly the fireResetEvent() of this class?
Regards, J�r�me. On 5/28/05, Kenny Chong <[EMAIL PROTECTED]> wrote: > You may use the 'reset' service. > > -----Original Message----- > From: J�r�me BERNARD [mailto:[EMAIL PROTECTED] > Sent: Friday, May 27, 2005 5:25 PM > To: Tapestry users > Subject: Templates (re)loading... > > 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]
