Login into our NG Application and executing a jasper report from within the application works just fine.
Waiting for a while and executing the report again, gives the following two error lines in the Browser log:
[Error] Failed to load resource: the server responded with a status of 403 (Forbidden) https://<subdomain>/login/sls/staticfiles/includes/bootstrap-theme.min.css.map
[Error] Failed to load resource: the server responded with a status of 403 (Forbidden) https://<subdomain>/login/sls/staticfiles/includes/bootstrap.min.css.map
Login out and login in again, and the report can be executed again.
Looks to me like the problem is related to a timeout. But I have no idea about the relation to bootstrap-theme.min.css.map, and bootstrap.min.css.map
Anyone having experienced this phenomena and can give a hint?
doesn’t ring a bell.
As executing the report is a Java process, running on the server, I don’t see how this is directly related to these errors.
If these kind of errors occur, than I would think not only the report generation, but more parts of your solution are suffering from this.
The issue might be in the steps happening after the report generation, for instance downloading/previewing the report.
Can you maybe elaborate on this report generation process and the steps involved?
Thanks for the good idea about the problem could be in the area of downloading/previewing the report. That would explain why we never had problems in Smart Client, but now problems in NG Client. It’s one of a few blockers which doesn’t allow us to switch off the Smart Client and really go with the NG Client.
I will investigate after my holidays if I can find what’s going on here.
Some things can look real challenging when moving from Smart Client to NG Client and you’re probably introduced to a whole new world looking at client-side of things.
Nevertheless, previewing/downloading PDF files should be easy using the PDF JS component.
Directly downloading the PDF file to the browser is even easier:
var _aBytes = plugins.jasperPluginRMI.runReport(.............)
plugins.file.writeFiel('myPreview.pdf' _aBytes);
we completely moved from smartclient to ng/ngdesktop, but reporting wasn’t an issue, apart from big reports that take a lot of time to render completely on the server, but apart from that we successfully generate pdf, docx and xlsx from jasper to
On a different note, the .map-files shouldn’t be a problem, i think they just make tracing the minified files easier, your solution should still run. We sometimes don’t get those either and everything just works fine.