ICEfaces-EE ACE Components Tag dataExporter. Utility to export data from a datatable as an Excel, PDF, XML or CSV document. This component renders an . GitHub clone of SVN repo / (cloned by ). This repo is not updated anymore. Please. The problem was due to missing the dependency liferay-faceslsvpatch version ga5. It was fixed by adding.
|Published (Last):||9 June 2011|
|PDF File Size:||1.59 Mb|
|ePub File Size:||11.98 Mb|
|Price:||Free* [*Free Regsitration Required]|
This component renders an HTML button element. More components and HTML elements can be nested inside this tag to give a different look and feel to the button. When the button is clicked, a file is generated with the requested data, and a new JSF Resource is created to serve that file. The URL to that Resource is then sent to the client, which automatically loads the file on the same page, without navigating away from it and without disturbing its state.
The data exporter has three required attributes: The following is an example of the basic usage. Also, one can nest other components or HTML markup inside the data exporter tag to modify the look and feel of the button.
In this case, the label will be rendered before all other components and markup, but only if it was explicitly specified i.
If a table is using stacked columns, it won’t affect iicefaces results of the exporting action. The data exporter is unaware of stacked columns.
TagLib Documentation This section covers attributes involved in the typical use-cases for this component. For reference, the complete taglib documentation for this component is available here. The supported attributes are the following:. The pageOnly iceefaces exports only the current page being displayed in the table, when using pagination.
The excludeColumns attribute accepts a icrfaces list datarxporter column indexes zero-relative to be excluded from the exporting. It can be modified dynamically. The userColumnOrder attribute is used to specify whether the columns should be exported according to the order established by the user in the client or according to the order in which the columns appear in the facelet. In the case of xls and pdf formats, one can use the preProcessor and postProcessor attributes to specify a method that will be invoked before or after the exporting, so that a developer can modify the document being delivered.
The method specified must accept an argument of type com. Document in the case of the pdf format, and an argument of type org. Workbook in the case of the xls format.
The encoding dataexportre is used to specify the character encoding to use. The default value is UTF The includeHeaders and includeFooters boolean attributes are used to specify whether the column headers and column footers are included in the exported file, respectively.
If the selectedRowsOnly attribute is set to true, only the selected rows in the table will be included in the exported file. This doesn’t work in conjunction with the pageOnly attribute. All selected rows in the entire table in all pages will be dataexporrer in the exported file.
dataExporter (ICEfaces Custom Components)
The “activate” event name is now deprecated but treated as an alias for “action” for backwards compatibility with existing applications.
Source code: Class DataExporter.java part of icefaces-ace version 3.1.0
In IE7 this mechanism isn’t supported, instead a new pop-up window is open and the file is loaded there. In order to support exporting files in PDF format, the iText library version 2.
For licensing reasons, the iText library is not included in the ICEfaces distribution bundles. If iceaces want to suport the XLSX format, the following libraries have to be in the classpath of your application: Apache XML Beans xmlbeans Powered by Atlassian Confluence 2. Printed by Atlassian Confluence 2. Table of Contents Loading