We are just starting up on a similar project using Turbine. In a nutshell, here is the technique I have developed:
I have a class called PdfScreen that extends VelocityScreen. The only purpose of this class is to set the layout to another new class called PdfLayout. A PdfScreen has an associated Velocity template that is an xsl:fo document. PdfLayout extends VelocityOnlyLayout. In the doBuild method of PdfLayout I process the screen using the Turbine ScreenLoader and render the resulting xsl:fo document using Fop. Then I send the results to the response. It all seems to work fairly well in testing, but we have yet to deploy anything to production and I have not thoroughly tested it under load. I thought about using Velocity to create xml and then apply an xsl stylesheet to create the xsl:fo, but decided to stick with Velocity and a two step process for now. I'd be happy to post some code snippets if you'd like. -- Steve Yokanovich Smyth Companies, Inc. In Phee, Martin J (Jump Tech) wrote: > Anyone using turbine for web based reporting? What tools are you using. > I've been using xml/xslt/fop for some reporting. Just wonder how others are > accomplishing it. > > Thanks, > > Marty > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
