what you can do is have wicket generate the necessary xml you need with wickettester and postprocess that yourself into the pdf.
you can override page#getmarkuptype() to return "xml" and wicket will look for the xml file instead of html. -igor On Mon, Dec 15, 2008 at 2:14 PM, Adrian Wiesmann <awiesm...@somap.org> wrote: > Hello everybody > > A quick question out of curiosity. Has anybody played around or tried to > generate XSL-FO from within your Wicket project? > > What I mean is this: > > - Add an XML file to every HTML file. > - Tell Wicket to use the XML instead of the HTML file for the markup. > - Have Wicket do the markup inheritance magic and "rendering" of a FO file > (instead of plain HTML). > - Use the resulting FO to render PDF with Apache FOP. > - Present the PDF file instead the HTML to the client. > > Anyone did so? Anyone played with Wicket and did so in a Swing application > (instead the web environment)? > > I know, these questions may sound strange, but I am currently thinking > about the possibilities of Wicket's markup inheritance and if it is > possible (and makes sense) to use Wicket as a reports generator. Not what > it is intended to do, but just pretend everything makes sense. :) > > Thanks for your comments. > > Cheers, > Adrian > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
