<div class="gmail_quote">On Thu, Mar 10, 2011 at 13:02, George Gastaldi <span dir="ltr"><<a href="mailto:gastaldi@apache.org">gastaldi@apache.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hello,<div><br></div><div>I have a new proposal for a new Seam 3 Module: <br><div><br></div><div>Seam Report: Integrate JasperReports, BIRT and other report solutions providing an unified bridge for compiling and populating data.</div>
</div></blockquote><div><br></div><div>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.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div><div>Could use some stuff already on Seam Mail (Velocity templates, for example) and also Flying Saucer (<a href="https://xhtmlrenderer.dev.java.net/" target="_blank">https://xhtmlrenderer.dev.java.net/</a>) for generating PDFs based on XHTML.</div>
</div></blockquote><div><br></div><div>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.</div>
<div><br></div><div>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.</div><div><br></div><div>-Dan</div><div><br></div>
<div>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.</div><meta http-equiv="content-type" content="text/html; charset=utf-8"><div>
</div></div>-- <br><div>Dan Allen</div>Principal Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br><br><div><a href="http://www.google.com/profiles/dan.j.allen#about" target="_blank">http://www.google.com/profiles/dan.j.allen#about</a><br>
<a href="http://mojavelinux.com" target="_blank">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction" target="_blank">http://mojavelinux.com/seaminaction</a><br></div><br>