[#14231] - jasperreports.properties require.js setting not taking effect

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 community@tibco.com with questions or issues requiring TIBCO review or response.

Category:
Bug report
Priority:
Normal
Status:
New
Project: Severity:
Minor
Resolution:
Open
Component: Reproducibility:
N/A
Assigned to:

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:

com.jaspersoft.jasperreports.components.customvisualization.require.js=/pathtorequire/js/lib/require-2.1.6.src.js
and resulted in a web page that references the correct location
<script class="jasperreports" src="/pathtorequire/js/lib/require-2.1.6.src.js" type="text/javascript"></script>

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:

<script src="net/sf/jasperreports/customvisualization/resources/require/require.js"></script>

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.

v6.18
plam_1's picture
2
Joined: Jan 27 2022 - 1:43pm
Last seen: 1 month 3 days ago
Feedback
randomness