Jaspersoft Community 'Read-Only' as of July 8, 2022
Transition to New TIBCO Community Just Weeks Away
You can still search, review wiki content, and review discussions in read-only mode. Please email firstname.lastname@example.org with questions or issues requiring TIBCO review or response.
We're in the process of upgrading jasperreports library from jasperreports-6.2.0 to jasperreports-6.19.1. It seems something changed in the handling of the com.jaspersoft.jasperreports.components.customvisualization.require.js and possibly net.sf.jasperreports.web.resource.pattern.customvisualization.scripts settings in the jasperreports.properties file. The previous version had a setting like this:
and resulted in a web page that references the correct location
using the new version of jasperreports library (6.19.1), with the same settings in jasperreports.properties, the part of the web page that references require.js now looks like this:
Did something change with this setting? We can get this to work by adding /net/sf/jasperreports/customvisualization/resources/require/require.js to tomcat so the file will get served from the requested location, but that is far from ideal.