Minor Description
Many people seem to be using Tapestry to render emails inside the applications.
With tapestry 3.0, it was possible to store the get the value of the current form attribute, create a writer, render a page inside the current RequestCycle (for generating the email) and finally restore the form attribute.
With all the changes in Tapestry 4, this process is not straightforward to translate, and also I think this process should be hidden inside the framework.
Suggestion: add a method inside the IRequestCycle (or another Tapestry service) to render a page to a writer.