Yes! Finally! I've been wanting to organize a module like this for a long time. In my experience, the business need that unites all companies is reporting. Yet, there's still a large gap between web application development and reporting engines. As I emphasize in my talk, if you can just give developers the API to inject, it opens up the world to that technology.

 

Cody, the Seam Mail lead, has been asking about our plans for PDF generation for a while. He has pointed out in the past that trying to retrofit XHTML for PDF generation really puts handcuffs on the developer. A much better approach, which is inline with the philosophy of Seam 3, is to create a really nice and accessible API for assembling a PDF. You get better looking reports with less effort in the end.

Try to catch each other on IRC and workout the scope of the module. Then seed the module and point us to it, and we'll pull it into the Seam repo.

-Dan

p.s. The licensing terms for iText may present a barrier to using it in Seam. PDFBox is more license friendly, though lacks some features.