JarCastingVraptor Jasper Report Plugin
Report Generation Plug-in for Vraptor
Supported File Formats:
- CSV
- XLS
- TXT
- ODT
- HTML
- DOCX
- RTF
- ODS
- PPTX
- XHTML
- XLSX
- IMAGE (PNG, JPEG, BMP)
Using it
- In a Maven project's pom.xml file:
<repositories>
<repository>
<id>sonatype-oss-public</id>
<url>https://oss.sonatype.org/content/groups/public/</url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
</snapshots>
</repository>
</repositories>
<dependency>
<groupId>br.com.prixma</groupId>
<artifactId>vraptor-jasperreport</artifactId>
<version>4.1.1</version>
</dependency>
- Put vraptor-jasperreport-version.jar Download Here and dependencies in your
WEB-INF/libfolder. - Create a class to represent your report: make it implement the
br.com.caelum.vraptor.jasperreports.Reportinterface. - In your controller, create an instance of your report and return it from your method
Controller
@Controller
public class ClientsController {
@Inject private final Result result;
@Inject private final Clients clients;
@Path("/clients/pdf")
public Download pdfReport() {
Report report = generateReport();
return new ReportDownload(report, pdf());
}
@Path("/clients/xls")
public Download xlsReport() {
Report report = generateReport();
return new ReportDownload(report, xls());
}
@Path("/clients/report")
public Report customReport() {
return generateReport(); //uses content negotiation to find export format
}
private Report generateReport() {
List<Client> data = clients.listAll();
return new ClientsReport(data);
}
}
Report
public class ClientsReport implements Report {
private final List<Client> data;
private Map<String, Object> parameters;
public ClientsReport(List<Client> data) {
this.data = data;
this.parameters = new HashMap<String, Object>();
}
public Report addParameter(String key, Object value) {
this.parameters.put(key, value);
return this;
}
public Collection<Client> getData() {
return data;
}
public String getFileName() {
return "report" + System.currentTimeMillis();
}
public Map<String, Object> getParameters() {
return this.parameters;
}
public String getTemplate() {
return "report.jasper";
}
public boolean isCacheable() {
return true;
}
}
Report Builder
Alternatively, you can use the ReportBuilder instead of creating a new class that implements Report once the builder does that for you. Additionally, it allows you to set only the properties you need for your reports.
The code in your controller would look something similiar to this one:
@Controller
public class ClientsController {
@Inject private final Clients clients;
[...]
private Report generateReport() {
return new ReportBuilder()
.withTemplate("report.jasper")
.withData(clients.listAll())
.with[...]
.build();
}
}
Batch Export
Several reports can be exported together to form a single resulting document.
public Download batchReport() {
BatchReportsDownload download = new BatchReportsDownload(pdf());
Report header = ...
Report content = ...
Report footer = ...
download.add(header, content, footer);
return download;
}
Note: Not all exporters can work in batch mode
Zip Export
This option allows you to export reports in different formats and agroup them into a single zip file.
public Download zipReport() {
ReportsDownload download = new ReportsDownload();
download.add(pdfReport, pdf())
.add(csvReport, csv())
.add(xlsReport, xls())
.add(docxReport, rtf())
.add(odtReport, odt());
return download;
}
Accept header
If your method return a report, an interceptor tries to discover the request format (through _format or Accept header) and then render the report in this format.
<a href="<c:url value="/clients/report?_format=csv"/>">CSV Report</a>
@Get("/clients/report")
public Report report() {
Report report = ...;
return report;
}
Exporting files
@Controller
public class ReportsController {
@Inject private FileSystemReportExporter exporter;
private File generateSingleFile() {
Report report = generateReport();
return exporter.export(report);
}
private File generateBatchFile() {
Report part1 = new MonthlySalesGrowthReport();
Report part2 = new TopItemSalesAnalysisReport();
exporter.export("filename", pdf(), part1, part2);
}
private File generateZipFile() {
ReportItem part1 = new ReportItem(new MonthlySalesGrowthReport(), pdf());
ReportItem part2 = new ReportItem(new TopCustomerAnalysisReport(), png());
ReportItem part3 = new ReportItem(new ItemSummaryWorksheetReport(), xlsx());
return exporter.export("sales_dashboard", part1, part2, part3);
}
}
Note: All files will be saved in the WEB-INF/tmp directory by default.
Embedding reports
Example:
@Get("/report/embed")
public void serializeReport(ReportSerializer serializer) {
Report report = buildReport();
serializer.serialize(report);
}
In your jsp:
$("#reportButton").click(function() {
$.getJSON('${pageContext.request.contextPath}/report/embed?_format=pdf', function(report) {
$('#container').html("<embed src=\"" + report.src + "\" width='900' height='800' />");
});
});
Note: The report content will be serializable as a base64 string, in accordance with RFC 2397.
Customizing Export Formats
Sample: Make all pdf reports encrypted.
@ApplicationScoped
@Specializes
public class EncryptedPdf extends Pdf {
public ExporterConfiguration getExporterConfiguration() {
exportConfiguration.setEncrypted(Boolean.TRUE);
exportConfiguration.set128BitKey(Boolean.TRUE);
exportConfiguration.setUserPassword("123456");
exportConfiguration.setOwnerPassword("123456");
return exportConfiguration;
}
}
Customizing paths
By default the lib will consider only reports under WEB-INF/reports folder, but you can also specify a different path format. For enabling this you must put this parameters on web.xml:
<context-param>
<param-name>vraptor.reports.path</param-name>
<param-value>custom reports path</param-value>
</context-param>
<context-param>
<param-name>vraptor.subreports.path</param-name>
<param-value>custom subreports path</param-value>
</context-param>
<context-param>
<param-name>vraptor.images.path</param-name>
<param-value>custom images path</param-value>
</context-param>
<context-param>
<param-name>vraptor.reports.generation.path</param-name>
<param-value>custom report generation path</param-value>
</context-param>
These folders are passed as parameters to reports:
`$P{REPORT_DIR}` directory where the reports are available
`$P{SUBREPORT_DIR}` directory where the sub-reports are available
`$P{IMAGES_DIR}` directory where the images are available
`$P{REPORT_GENERATION_PATH}` directory where the output file are available
So, to include an image in the report just do: $P{IMAGES_DIR} + "image.png"
Decorating reports
Decorators can be used to provide default parameters for all reports, like this
@SessionScoped
public class LoggedUserInjector implements ReportDecorator {
@Inject private final LoggedUser user;
public void decorate(Report report) {
report.addParameter("GeneratedBy", user.getName());
}
}
Now all reports have a parameter called $P{GeneratedBy}.
Using Result
Another way to pass parameters to your report is through the result object. Values passed to the result are automatically converted into parameters
@Get("/clients/report")
public Report report() {
result.include("GeneratedBy", user);
Report report = generateReport();
return report;
}
SQL Query Reports
If your reports are set to run the SQL query internally, you can pass the report a Connection to use by adding a parameter with the name of 'java.sql.Connection' and the actual connection as the value, like this:
Connection con = [...]; // <- return a valid connection here
report.addParameter("java.sql.Connection", con);
Or, you can take advantage of the Decorators feature and create one like this:
@ApplicationScoped
public class SQLReportDecorator implements ReportDecorator {
@Inject private EntityManager em;
public void decorate(Report report) {
report.addParameter(Connection.class.getName(), getConnection());
}
private Connection getConnection() {
final Session session = (Session) em.getDelegate();
final SessionFactoryImpl sessionFactory = (SessionFactoryImpl) session.getSessionFactory();
try {
return sessionFactory.getConnectionProvider().getConnection();
} catch (SQLException e) {
return null;
}
}
}
Internationalization
JasperReports lets you associate a java.util.ResourceBundle with the report template, at runtime (by providing a value for the built-in REPORT_RESOURCE_BUNDLE parameter). If your report needs to be generated in a locale that is different from the current one, the built-in REPORT_LOCALE parameter can be used to specify the runtime locale when filling the report. You just need to put a file called i18n_en_US.properties (or whatever) in the same folder of your reports. Having done this, parameters such $R{text.message}, will be automatically converted to the expected language.
For changing this you must put this parameter on web.xml:
<context-param>
<param-name>vraptor.reports.resourcebundle.name</param-name>
<param-value>custom resource bundle name</param-value>
</context-param>
Image Servlet
This servlet (included in the JasperReports distribution package) is needed as part of your Web application in order to include images in your HTML reports. To map this servlet to serve the images that are included in yours report, just do:
<servlet>
<servlet-name>ImageServlet</servlet-name>
<servlet-class>net.sf.jasperreports.j2ee.servlets.ImageServlet</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>ImageServlet</servlet-name>
<url-pattern>/report.image</url-pattern>
</servlet-mapping>
Dependencies
- Commons Logging http://jakarta.apache.org/commons/logging/
- Commons Collections http://jakarta.apache.org/commons/collections/
- Commons BeanUtils http://jakarta.apache.org/commons/beanutils/
- Commons Digester http://jakarta.apache.org/commons/digester/
- JFreeChart http://www.jfree.org/jfreechart/ - Only required when the report contains charts
- iText http://www.lowagie.com/iText/ - Only required when exporting reports to PDF or RTF
- Jakarta POI http://jakarta.apache.org/poi/ - Only required when exporting reports to Excel format
- JExcelApi http://jexcelapi.sourceforge.net/ - Only required when exporting reports to Excel format