Essentially you're talking about capturing the output of a page / component / block and serialising it to a String, of which there has been plenty of past discussion here on the mailing list.
Though personally, my technique would be to render the dev-mode error page into to your prod-mode error page, convert the component generated markup into a String (to be emailed) and then remove the XML from the DOM. I give a lot more detail (and worked example) here: http://tapestry.1045711.n5.nabble.com/Rendering-a-Block-td3401393.html#a4457710 Emailing stacktraces and xml is easy - I've never had any probs with apache commons email - but remember, you'll need to send a multi-part MIME email for HTML and attach the error page stylesheets to it. Steve. On 22 October 2011 07:01, Wechsung, Wulf <wulf.wechs...@sap.com> wrote: > Hello all, > > I will open up my t5 intranet application for "public" testing next week and > was planning on having slf4j send me all exception stack traces that occur > per email. I was wondering if it's possible to do the same for the glorious > tapestry error page. Even more awesome would be to be able to do this in > production mode (ie non-production mode error page sent by email while > showing the user the production-mode error page). Is this at all possible? > > Best Regards, > Wulf > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
