Visualize.js Highcharts naming collision

0

In our current application, we're using the highcharts library and an angular directive to display a line chart in one section. I am now adding JasperServer as a reporting solution and attempting to use VisualizeJS in a separate section. The library loads fine when I include the scripts in such an order like,

<script src="https://code.highcharts.com/highcharts.src.js"></script> <script src="/bower_components/highcharts-ng/dist/highcharts-ng.min.js"></script> <script src="http://<jasperserver-ip>/jasperserver-pro/client/visualize.js"></script> <script src="/js/application.js"></script>

When I navigate to the area I'm attempting to embed a JS report, calling visualize like,

visualize(function (v) {
  var report = v.report({
    resource: "/organizations/organization_1/reports/Run_Event_Report",
    container: "#container",
    params: { "site_name" : [ "Site1" ] },
    events: {
      reportCompleted: function(status) {
        console.log(status);
      }
    }
  });
}, function(err) {
  console.log(err);
});

results in Highcharts throwing an error "Uncaught Error: Highcharts error #16: www.highcharts.com/errors/16" which is likley because the Highcharts library is being loaded twice. It seems that VisualizeJS isn't serving up the Highcharts library to the client so I need to keep Highcharts and the directive scripts in the HEAD. I also tried changing the order so VisualizeJS is loaded first, but that doesn't make any difference. What should I do?

mana135's picture
Joined: Aug 18 2016 - 12:11pm
Last seen: 2 years 7 months ago

Yes, it certainly appears that Highcharts is being loaded twice here. Have you logged a case around this yet? I'm happy to look into this.

dpetzold - 2 years 8 months ago

No I have not logged a case. I'm not sure how to do that.

mana135 - 2 years 8 months ago

In the main menu here you will see "Tracker". Select this and the "Create new Bug Report" hyperlink. This is very helpful as we are reviewing this.

dpetzold - 2 years 8 months ago

0 Answers:

No answers yet
Feedback
randomness