You cannot create a report if you do not have a compiled JasperReports design file and the code for driving the report.
Use EGL ReportLib functions to write report-invocation code in your EGL project. You can use the EGL Program Part wizard when creating report-invocation code.
EGL automatically generates Java™ code from the EGL report handler (if you created one) and from the EGL report driver. (EGL compiles the XML design file into a .jasper file automatically each time you save it. You can force EGL to recompile XML design file by selecting Project > Clean.)
As the EGL program runs, the JasperReports program used by EGL first fills and stores a .jrprint file. This file uses an intermediate file format that the program will then export into the final report format (.pdf, .html, .xml, .txt, or .csv).
myReport.ReportExportFile = "C:\\temp\\my_report.pdf"; reportLib.exportReport(myReport, ExportFormat.pdf);
EGL does not automatically refresh exported reports. If you change the report design or if data changes, you must run the report driver again.
Related concepts
EGL reports overview
Related tasks
Creating an EGL report handler
Creating the report design file
Exporting reports
Generating files for and running a report
Using report templates
Using the EGL templates with content assist
Writing code to drive a report
Related Reference
EGL library ReportLib
EGL report handler
The XML source file should have a .jrxml extension. Be sure to save the XML design document in the same EGL package that will contain the report driver code files and the EGL report handler (if you use one).
The EGL runtime will automatically compile a valid XML source file into a JasperReports design file each time you save the source to disk (provided you have the javac compiler on your execution path). If you do not create a new .jrxml file, you must import a previously compiled .jasper file.