Details
-
Type:
Feature Request
-
Status: Open (View Workflow)
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: The Future
-
Component/s: None
-
Labels:None
Description
Seam 2 provided PDF and Excel rendering directly via facelets, I was heavily impressed by this feature, and it is widely used in our projects.
How to use it in Seam3(I am sorry, I do not know it should belong to Faces module or this module)?
Gliffy Diagrams
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
For pdf rendering, there are several open source solutions existed, Apache FOP(I used it and transformed xml file to pdf directly, especially DocBook files), Apache PDFBox, iText, and ICEPDF(it is from the famous ICEFaces company, I have not used it).
For Excel exporting, JExcel is simple and easy, but Apache POI is powerful, and it is not only for Excel now, it is also support other MS Office format.
hantsy bai
added a comment - For pdf rendering, there are several open source solutions existed, Apache FOP(I used it and transformed xml file to pdf directly, especially DocBook files), Apache PDFBox, iText, and ICEPDF(it is from the famous ICEFaces company, I have not used it).
For Excel exporting, JExcel is simple and easy, but Apache POI is powerful, and it is not only for Excel now, it is also support other MS Office format. Check the XDocReport implementation in the develop branch (Will be available on the Beta1) and let me know if this feature is enough. Basically it reuses a DOCX or ODT document as the report itself.
The project is in http://code.google.com/p/xdocreport/
George Gastaldi
added a comment - Check the XDocReport implementation in the develop branch (Will be available on the Beta1) and let me know if this feature is enough. Basically it reuses a DOCX or ODT document as the report itself.
The project is in http://code.google.com/p/xdocreport/ 
We are using the functionality (easy templating through facelets) a lot in our SEAM 2 projects. I hope this terrific feature can be included in SEAM reports.
What about licensing issues with iText? Are Jasperreports and pendaho not using iText too as their PDF renderer? Are we going to stick to certain version of iText or are you looking for an alternative?