Yes iText "new" license could cause some trouble. I could stick with iText v4.x
but it is end of life
Maybe rewrite the tags with the PDFBox library instead of iText?
Or maybe you know another FOSS lib for that?
Le 2012-08-31 11:12, Gaël Beaudoin a écrit :
Le 31/08/2012 17:02, Denis Forveille a écrit :
> What thing we like in seam 2 is the pdf engine based on JSF components taylored for
> As we are moving to CDI, we a re looking for an equivalent engine to produce PDF
> Seam 3 does not seem to have such an engine ready
> Flyingsaucer (http://code.google.com/p/flying-saucer
) is almost doing this except
that it uses plain JSF/faelets tags, not specific
> iText tags/components
> I'm thinking on writing such an engine, based on reusing the seam2 JSF-iText
tags/components and on the principle described here:
> - write an xhtml report with the seam 2 JSF/iText tags/components exactly as in seam
> At runtime, have a filter that intercepts the request for such a PDF document (based
on extension or request parameter), forward the
> request to the JSF engine as a standard request to compose the response
> -> the tags will generate a iText document and attach it in a scoped
> - the filter read the iText object, and read send it to the reponse object
> use something similar to what ios described here for rendering the response
programatically : http://www.bradchen.com/node/36
> This engine would obviously depends on JSF and iText, and maybe on CDI
> Does this already exist?
> seam-dev mailing list
Sounds like a great idea. We're already using the seam 2 version and
it's simple and useful. Which version of iText would you use though?
Isn't the new license a problem ?
seam-dev mailing list