lukaszlenart opened a new pull request, #1924: URL: https://github.com/apache/struts/pull/1924
Fixes [WW-5734](https://issues.apache.org/jira/browse/WW-5734) ## Why The jasperreports7 plugin had never been exercised outside Spring's `MockHttpServletResponse` — no sample app uses it — which is how WW-5731, WW-5732 and WW-5733 (every export an empty `200` on Tomcat) shipped unnoticed since 7.1.0. The showcase can't host an example: JasperReports is LGPL and the showcase WAR is part of the release assembly (the previous example was removed for that reason in 2006). ## What `JasperReport7TomcatTest` boots Struts on `tomcat-embed-core` (**test scope**, 10.1.55, bound to 127.0.0.1 on a random port), compiles the existing `simple.jrxml` into the webapp's docBase under `target/`, and issues a real HTTP `GET /report.action?format=…` for each of the six bundled formats, asserting status, content type and payload (`%PDF`, `{\rtf`, `PK`, or the rendered text). Runs in ~1 s as part of the module's normal surefire run, under both the default and the `jakartaee11` profile. With the exporter providers reverted to their pre-WW-5733 state, all six assertions fail with an empty body — the real container symptom the mock could not show. Test-only change: nothing here reaches the plugin jar or the assembly (`runtime` dependency sets), and the OWASP profile skips test scope. 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
