Hello list,
I am trying to extend an existing Turbine application by a "Download" link which should result in a PDF file being served, containing the same data as in the screen template counterpart. Take a video database for instance, I can browse through the video titles and have a look at specific videos by looking at their "Details.vm" screen template which would output detail information. Alternatively, I would like to offer a "Download as PDf" link which should resemble the screen output, but was assembled via FOP, presenting the video details as a sort of "video data sheet". With regards to the PDF generation, I am presented with the same problems as in the course of the template screen generation: - using the l10n mechanism - possibly using other pull tools Therefore it would be very reasonable to use these template services in a page which does NOT output to the HTTPServlet-request-OutputStream, but instead is able to - set a MIME-Type - gather the output of the template (in which I can use the beloved set of pull tools, e.g. for internationalization), which delivers a FO String - pipe the generated FO String (or Stream) through a FO->PDF converter - stream the PDF byte stream into the servlet output How can I achieve this in Turbine? The FO->PDF conversion poses no problem (in fact: is already working), but how can I tell Turbine to use the template mechanism with all pull tools but capturing the output in order to send it into the FO->PDF converter and stream it back? I suppose, this has to be a special Page class capable of doing this. Could you point me in the right direction? TIA, Alex
