-
1. Re: Excel Export with rich:dataTable
baz Mar 10, 2008 8:57 AM (in response to bibinsga25)I am also interested in this subject. Export a generic datatable to spreadsheet(CSV-Data) With an additional Excelcompatible switch.
I would prefer to see a native richfaces implementation.
A related Question: How can i capture an generic part of the HTML-Page.
Similiar to tomahaks t:buffer, which i can not use. If we are able to capture html we can feed this html to excel and we are ready. -
2. Re: Excel Export with rich:dataTable
bibinsga25 Mar 10, 2008 9:42 AM (in response to bibinsga25)Actually I tried using the t:dataTable and excelExport component together in my RichFaces,Faceletes application.But the table didnt got rendered.Do I need to define the Myfaces extensions filter to enable the component in my application.?? Do I need to do anything else??Please suggest?
-
3. Re: Excel Export with rich:dataTable
chris.simons May 22, 2008 1:49 PM (in response to bibinsga25)Has anyone had any lucking using this sandbox component with a RichFaces dataTable?
Vote!
http://jira.jboss.com/jira/browse/RF-724 -
4. Re: Excel Export with rich:dataTable
sergeysmirnov May 22, 2008 2:04 PM (in response to bibinsga25)"chris.simons" wrote:
http://jira.jboss.com/jira/browse/RF-724analogue of tomahawk's t:buffer tag
I am really not understand what the practical reason for that if you use JSF for the purpose it is designed for. -
5. Re: Excel Export with rich:dataTable
chris.simons Aug 13, 2008 3:39 PM (in response to bibinsga25)
The purpose of JSF, in my eyes, is to add a view layer that makes building applications - large and small - a thing of beauty.
When building an application for commercial or government enterprises, users "require" certain things. When dealing with applications that present a lot of data, users often ask for ways to export that data to other formats. Excel and PDF are too common examples. What better way to extend the already powerful RichFaces library than to add these types of functionality *built-in* to the dataTable component?
You could also argue that this type of functionality is best served by a true reporting engine (Jasper, JReport, Crystal, etc.). I would agree with this statement. Sometimes, though, money and time for COTS integration isn't always an option.