JasperReportsIntegration provides an interface to use the JasperReports reporting engine in an Oracle database application, specifically with Oracle Application Express (Oracle APEX).
As Fernando suggested, a report should be deployed by using the .jrxml instead of the .jasper file. It could be compiled on the fly.
I would like to modify the requirement, already had it on my mind for a long time. The integration should be able to pick up either the .jrxml source file OR the .jasper comiled version.
First we need to find the .jrxml and .jasper files. Both might exist or just one of them. Then we compare the file dates.
if the .jasper file is newer than the .jrxml file => run the .jasper file
if the .jrxml file is newer than the .jasper file => compile the .jrxml file to the .jasper file and run that
This way:
Existing functionality does not break, people can still deploy there .jasper files
People can now just deploy the source file. One additional step (compilation) is omitted
People are allowed to make mistakes. If they deploy a new .jrxml file and an old .jasper file ... the newer .jrxml will be picked up and the old .jasper file will get replaced.
Makes the transition to a new JasperReports version easier. Just delete the .jasper files and have the reports recompiled using the latest library version.
daust
commented
4 years ago
As Fernando suggested, a report should be deployed by using the .jrxml instead of the .jasper file. It could be compiled on the fly.
I would like to modify the requirement, already had it on my mind for a long time. The integration should be able to pick up either the .jrxml source file OR the .jasper comiled version.
First we need to find the .jrxml and .jasper files. Both might exist or just one of them. Then we compare the file dates.
This way: