Clear differences between normal http way of embedding vs visualize.js way of embedding?


I would like to know what are the exact differences between the way we embed report susing HTTP based way vs embedding by visualize.js.

Is there any performance issue? I stil see its taking time to load when used using visualize.js.



gowthamsenmca's picture
Joined: Oct 15 2013 - 4:52am
Last seen: 6 years 6 months ago

2 Answers:

There should not be performance differences in theory.

See this article for a comparison:

kkumlien's picture
Joined: Jan 22 2015 - 4:36am
Last seen: 2 weeks 6 days ago

What do you mean by "HTTP based way"? Visualize.js is just a Javascript library using ajax calls to JasperReports Server.

If you mean difference between using "iframe" and Visualize.js, the main difference is Visualize.js uses <div> tags instead of <iframe>. As such, it's possible to add effects like in the following page (in Japanese). Try dragging reports from the top to one of the three boxes at the bottom. Drag the report around. Try stretching the report by dragging the triangle at the bottom right hand side of the boxes.

Another difference may be that Visualize.js may be using async processing while the regular JasperReports Server uses sync processing. Sync processing slows down the server very much when under heavy load (i.e. large report generation, many users).

hozawa's picture
Joined: Apr 24 2010 - 4:31pm
Last seen: 3 years 9 months ago