I guess the next step is to simulate the HTTP request and then grab the output from it. For generating html emails you wouldn't want to do any interaction through the web browser to initiate the page creation.
Maybe the wget approach is a good angle of attack, but needs to be closer to the App Server. Perhaps there is a website load testing tool that simulates requests/allows variables to be set that could be run on the same or different application server. Totally independent of Tapestry, like wget. The response can then be cat'd to the emailing service/print ad/fax machine, etc. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
