You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I deployed Jasper Integration jri-2.7.1-jasper-6.16.0 on tomcat 9 . after deploying unable to run the report getting following error
java.lang.RuntimeException: Class not found when loading object from file: c:\jri27\reports\ligitime\cashrep.jasper.
de.oc.utils.Utils.throwRuntimeException(Utils.java:18)
de.oc.integration.jasper.webapp.ReportWrapper.service(ReportWrapper.java:265)
javax.servlet.http.HttpServlet.service(HttpServlet.java:779)
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
where my .jasper and .jrxml both file in same directory. report run nicely from jasper studio. some reports are also running but some are not running please guide me
The text was updated successfully, but these errors were encountered:
Do you still have this issue?
Are you calling a subreport from a main report?
Do you get the same issue when running one of the test or demo reports?
Thanks
Can you provide a simplified test based on a data dictionary query like select * from user_objects?
Then I can have a look. Without any more information, I cannot troubleshoot the issue. Thank you.
I deployed Jasper Integration jri-2.7.1-jasper-6.16.0 on tomcat 9 . after deploying unable to run the report getting following error
java.lang.RuntimeException: Class not found when loading object from file: c:\jri27\reports\ligitime\cashrep.jasper.
de.oc.utils.Utils.throwRuntimeException(Utils.java:18)
de.oc.integration.jasper.webapp.ReportWrapper.service(ReportWrapper.java:265)
javax.servlet.http.HttpServlet.service(HttpServlet.java:779)
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
where my .jasper and .jrxml both file in same directory. report run nicely from jasper studio. some reports are also running but some are not running please guide me
The text was updated successfully, but these errors were encountered: