#104 have Spindle call Tapestry reset-service after rebuild

[Anonymous]

Tapestry has an option to run without caching, to be
used during testing, in order to see changes to
templates and specifications immediately. Turning on
the option makes it much slower however, and also leaks
quite a lot of memory (at least with our app on WAS).

An alternative approach is to not turn off the cache
entirely, but instead clear the cache on demand, using
the reset-service already present in Tapestry (if
turned on). This can be done manually by asking a
separate browser window for something like this:

http://localhost:9080/myapp/app?service=reset/nonexistingpage

Typically one would do this after an edit action with
Spindle.

After this long introduction finally comes the actual
feature request:

What I would like to be able do is to specify the url
as a property of a Tapestry project, and have Spindle
do what I now do manually (ping the reset service)
after a succesful Tapestry project rebuild.

Spindle creating this URL automatically would be nice,
but not too important.

Luc (ljgp@xs4all.nl)

[Geoffrey Longman]

Logged In: YES
user_id=387057

Sorry this has been delayed. I'm up to my neck in working
the current codebase into a form that will make it easier to
implement support for Tapestry 3.1 And since Tapestry 3.1 is
going alpha real soon now, that work takes precedence.