Weave Code
Jasper Report Bundle Laravel Package
sigedi/jasper-report-bundle
A Symfony bundle that integrates JasperReports into your app, letting you configure report templates, pass parameters, and export PDF, HTML, Excel, and other formats from services or controllers with minimal setup.
Symfony 6 / Symfony Flex Bundle integrating the Jaspersoft REST v2 client (jaspersoft/rest-client)
Frequently asked questions about Jasper Report Bundle
- Can I use sigedi/jasper-report-bundle in a Laravel application?
- Not directly. It is a Symfony bundle whose service definitions and DI extension depend on Symfony's kernel and container compilation, which Laravel does not run. For Laravel you should require the underlying jaspersoft/rest-client package directly and wire it in a service provider. The bundle remains useful as a reference for how to configure and call that client.
- What is sigedi/jasper-report-bundle used for?
- It integrates JasperReports into Symfony applications so you can compile .jrxml or .jasper templates, fill them with PHP data, and export reports to PDF, HTML, XLSX and other formats. It wraps the Java reporting engine behind configurable Symfony services so report generation feels native to the app. Configuration covers JasperReports paths, binaries and template locations.
- Does this package support Laravel 10, 11 or 12?
- There is no Laravel integration layer in the package, so Laravel version support is not something the bundle provides or tests. Compatibility for Laravel 10 to 12 depends on jaspersoft/rest-client, your PHP version and your Guzzle version. Pin that client explicitly rather than relying on it arriving transitively through a bundle you do not install.
- How do I generate JasperReports PDFs from Laravel?
- Require jaspersoft/rest-client with Composer, bind its configuration in a service provider, and call the REST endpoints that compile and render reports. Keep JasperReports Server connection details in config and run rendering through queued jobs, because report generation can be slow. The bundle's Symfony configuration is a useful reference for which settings the client needs.
- What export formats does the bundle support?
- The README lists PDF, HTML and XLSX, and other formats are available through JasperReports itself. Actual output depends on the exporter configured on the JasperReports Server side and on the report template. The bundle does not add formats beyond what the reporting engine produces.
- Do I need a running JasperReports Server or just Java installed?
- You need JasperReports Server, or the reporting engine and its tooling, available to the application, not merely a JVM on the web host. The bundle configures paths and binaries and then talks to that installation. Plan for JVM operations, licensing, JDBC drivers and REST API versioning, because the bundle does not insulate you from any of them.
- Is sigedi/jasper-report-bundle actively maintained?
- Public adoption is low, with zero stars, a single organisation and no independent validation, so bus factor is effectively one. Release 2.0.2 moved service definitions from XML to YAML, which suggests deliberate maintenance and tracking of modern Symfony conventions rather than an abandoned or generated project. Still verify the composer.json constraints yourself before relying on it, and keep the vendoring escape hatch in mind.
- What changed in versions 2.0.0 and 2.0.2?
- Version 2.0.2 switched the bundle's internal DI resource from services.xml to services.yaml, an implementation detail of Symfony container compilation. The 2.0.0 major bump predates it and is where breaking changes to configuration keys or the DI extension alias would live, so re-read the config tree if your notes came from 1.x. Neither release affects a Laravel application at runtime.
- How do I test JasperReports output without a production server?
- Point the client at a test or containerised JasperReports Server instance and assert on rendered bytes and status codes rather than on bundle internals. Keep report templates in version control and compile them as part of test fixture setup. A single end-to-end render is enough to confirm credentials, template paths and exporter settings.
- What are the alternatives to this bundle for report generation in Laravel?
- You can use jaspersoft/rest-client directly, which is the recommended path, or call the JasperReports Server REST API with Guzzle yourself. If JasperReports is not a hard requirement, native PHP PDF and spreadsheet libraries avoid the JVM and server licensing entirely. The bundle itself is only a fit if you are running Symfony.
Weaver
How can I help you explore Laravel packages today?