Excellent ! How about we form a team to that ? Cody, Dan, are you available on joining this project ?<br><br><div class="gmail_quote">2011/3/11 Cody Lerum <span dir="ltr"><<a href="mailto:cody.lerum@gmail.com">cody.lerum@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Though it might be a little odd, using freemarker or velocity to<br>
generate the xhtml for Flying Saucer might be an option.<br>
<br>
With regards to iText I had the same thought. However, the Flying<br>
Saucer guys make it clear they understand the licensing issue and are<br>
staying on the LGPL version. Guessing a fork of iText LGPL will take<br>
off at some point.<br>
<br>
PDFBox is just sorely lacking in the creation API's. No support for<br>
creating tables for example.<br>
<br>
-C<br>
<div><div></div><div class="h5"><br>
On Fri, Mar 11, 2011 at 1:39 PM, Dan Allen <<a href="mailto:dan.j.allen@gmail.com">dan.j.allen@gmail.com</a>> wrote:<br>
> On Thu, Mar 10, 2011 at 13:02, George Gastaldi <<a href="mailto:gastaldi@apache.org">gastaldi@apache.org</a>> wrote:<br>
>><br>
>> Hello,<br>
>> I have a new proposal for a new Seam 3 Module:<br>
>><br>
>> Seam Report: Integrate JasperReports, BIRT and other report solutions<br>
>> providing an unified bridge for compiling and populating data.<br>
><br>
> Yes! Finally! I've been wanting to organize a module like this for a long<br>
> time. In my experience, the business need that unites all companies is<br>
> reporting. Yet, there's still a large gap between web application<br>
> development and reporting engines. As I emphasize in my talk, if you can<br>
> just give developers the API to inject, it opens up the world to that<br>
> technology.<br>
><br>
>><br>
>> Could use some stuff already on Seam Mail (Velocity templates, for<br>
>> example) and also Flying Saucer (<a href="https://xhtmlrenderer.dev.java.net/" target="_blank">https://xhtmlrenderer.dev.java.net/</a>) for<br>
>> generating PDFs based on XHTML.<br>
><br>
> Cody, the Seam Mail lead, has been asking about our plans for PDF generation<br>
> for a while. He has pointed out in the past that trying to retrofit XHTML<br>
> for PDF generation really puts handcuffs on the developer. A much better<br>
> approach, which is inline with the philosophy of Seam 3, is to create a<br>
> really nice and accessible API for assembling a PDF. You get better looking<br>
> reports with less effort in the end.<br>
> Try to catch each other on IRC and workout the scope of the module. Then<br>
> seed the module and point us to it, and we'll pull it into the Seam repo.<br>
> -Dan<br>
> p.s. The licensing terms for iText may present a barrier to using it in<br>
> Seam. PDFBox is more license friendly, though lacks some features.<br>
><br>
> --<br>
> Dan Allen<br>
> Principal Software Engineer, Red Hat | Author of Seam in Action<br>
> Registered Linux User #231597<br>
><br>
> <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>
><br>
><br>
</div></div>> _______________________________________________<br>
> seam-dev mailing list<br>
> <a href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
><br>
><br>
</blockquote></div><br>