You can use a file with the .xml extension for your source, though this could slow your compilation. JasperReports recommends the .jrxml extension.
The following sections offer specifics for the different types of XML source files. This information covers very simple cases; for more complex examples see either the JasperReports Web site mentioned earlier or the documentation for your design tool (if you decide to use one).
<queryString><![CDATA[SELECT * FROM Table_Name]]></queryString>
<field name="Field_Name" class="java.lang.class_type"></field>
<textFieldExpression class="java.lang.class_type"><![CDATA[$F{Field_Name}]]></textFieldExpression>
<field name="Field_Name" class="java.lang.class_type"></field>
<textFieldExpression class="java.lang.class_type"><![CDATA[$F{Field_Name}]]></textFieldExpression>
<field name="Field_Name" class="java.lang.class_type"></field>
<textFieldExpression class="java.lang.class_type"><![CDATA[$F{Field_Name}]]></textFieldExpression>
EGL places the compiled .jasper file in the JavaSource\package_name directory that is parallel to EGLSource\package_name. When you successfully generate your EGL report driver, the product places a linked copy of the .jasper file in the parallel bin\package_name directory. You can force the .jasper file creation and copy by selecting Project > Build All or Project > Clean.
If you are creating an XML design document and a report handler simultaneously, see EGL report creation process overview for guidelines. For an example that shows how an XML design document gets a report data record from the report handler, see Creating an EGL report handler.
Related conceptsEGL reports overview
EGL report creation process overview
Related tasks
Creating an EGL report handler
Writing code to drive a report
Related reference
EGL library ReportLib
Data types in XML design documents