- Is hboie/jasper-report-bundle a Laravel package?
- No, it is a Symfony bundle, not a Laravel package. It ships no ServiceProvider, facade, publishable config, or config/*.php, and its integration surface is Symfony kernel bundle registration and the DI Configuration tree. For Laravel, treat it as a reference implementation and bind the framework-agnostic jaspersoft/rest-client yourself.
- Can I install hboie/jasper-report-bundle in Laravel with Composer?
- Composer can pull the package, but installation is not integration. The bundle expects Symfony kernel registration and a Configuration tree, so Laravel will not auto-discover, configure, or publish anything for it. You need a custom service provider around the underlying REST client, and php artisan vendor:publish will not help.
- How do I generate JasperReports from Laravel?
- Bind jaspersoft/rest-client in a small custom Laravel service provider and move JASPER_HOST, JASPER_USER, and JASPER_PASSWORD into config/services.php plus .env. Wrap the client behind a single JasperReportService so controllers and jobs never touch vendor code. Set explicit Guzzle connect and read timeouts, and use Laravel's Http::fake for tests.
- Does hboie/jasper-report-bundle support Laravel 10 or Laravel 11?
- There is no declared Laravel support because the bundle targets Symfony 2 through 5 only, and Symfony 5 reached end of life in November 2023. Release v1.6 does not appear to widen that support matrix. For Laravel 10 or 11, use the framework-agnostic jaspersoft/rest-client behind your own adapter instead of expecting bundle compatibility.
- How do I compile JRXML templates to .jasper files with this bundle?
- The bundle compiles .jrxml templates to .jasper files by wrapping JasperStarter and the Java reporting engine, using binary paths from its Symfony configuration. That configuration layer does not travel to Laravel, so you must invoke JasperStarter or the Jaspersoft REST API yourself. Keep compilation in a queued job if templates are large, and verify the Java runtime is installed on every environment.
- What export formats does hboie/jasper-report-bundle support?
- The bundle exposes JasperReports export formats including PDF, HTML, and XLS, plus other formats the underlying engine supports. The export format is chosen at report generation time and depends on your JasperReports version and template design. In a Laravel adapter, validate requested formats against an allowlist before passing them through.
- How do I configure JasperReports paths and binaries in Laravel?
- You cannot use the bundle's Symfony Configuration tree in Laravel, so replicate only the options you need in config/services.php or a dedicated config/jasper.php backed by .env. Store the JasperStarter path, Java path, Jaspersoft host, credentials, and timeouts there. The v1.6 timeout option is Symfony-only, so enforce timeouts at the Guzzle or Laravel Http client layer per report.
- How should I test JasperReports integration in Laravel?
- Avoid hitting a live Jaspersoft server in tests; use Laravel's Http::fake to stub REST endpoints and assert request payloads, auth headers, and timeouts. For JRXML compilation, mock your wrapper service or use a committed fixture .jasper file. Keep a separate integration suite against a disposable Jaspersoft environment for release checks.
- Is hboie/jasper-report-bundle safe for production?
- Technical risk is high: the project has one release in roughly 4.5 years, v1.6 adds only a timeout option, the declared Symfony 2-5 support matrix is entirely end-of-life, and it has 0 dependents and 5 stars. It is a thin HTTP wrapper over a licensed enterprise product, so replacing it is cheap, but you will own the Laravel adapter permanently. Treat v1.6 as a maintainer-is-alive signal, not proof of production safety, and confirm your Jaspersoft server version, auth model, and long-term reporting ownership first.
- What are alternatives to hboie/jasper-report-bundle for Laravel?
- The practical alternative is to use jaspersoft/rest-client directly inside a small Laravel service provider, or call the Jaspersoft REST API through Laravel's Http client. If you are greenfield, evaluate the reporting engine decision first, including JasperReports Server licensing, hosted BI options, and Laravel-native reporting tools. The Symfony bundle is a reference implementation, not the dependency to install.