## Release Notes

### Version 2.5.0.1 30.09.2018

- Moved to Github for Issue Tracking ( https://github.com/daust/JasperReportsIntegration ). Source code and files will be moved later.
- Further details on the changes can be found here: https://github.com/daust/JasperReportsIntegration/issues
- New features

- FEATURE: #1 - Upgrade to JasperReports 6.7.0
- FEATURE: #9 - Ability to set Printjob name (programmatically)
- FEATURE: #13 - Upgrade to JDBC libraries for Oracle 12 / 18.x

- Bug fixes

- BUG: #12 - encryptPasswords throws exection
- BUG: #11 - Issues with Glassfish

- Changed behaviour

- The minimum requirement is now a Java JRE 8 because JasperReports requires this starting with release 6.6.0. See the change log at the bottom.

### Version 2.4.0.0 15.10.2017

- BUG: #3939 - Built-in report functions not working due to missing library jasperreports-functions-$version.jar
- BUG: #3940 - printerDiagnostics abort when supported attribute values cannot be retrieved for category
- FEATURE: #3707 - Upgrade to JasperReports 6.4.1
- FEATURE: #3941 - Support for timeZones (report parameter REPORT_TIME_ZONE)
- FEATURE: #3942 - test.jrxml - list of user objects removed - timeZone displayed

- in order to see a change here you have to copy the new version of the following files into your reports folder:

- test.jasper
- test.jrxml

### Version 2.3.0.1 05.10.2015

- BUG: #294 - Fixed chunked encoding problem in xlib_http.get_report

- Many people have been struggling with this issue, mainly due to a problem when using the embedded pl/sql gateway: http://daust.blogspot.de/2011/01/issue-with-jasperreportsintegration-and.html

- FEATURE: #298 - Java runtime version and JasperReports version now included in J2ee homepage / index.jsp

- The homepage of the j2ee application includes more details about the current environment, this helps with troubleshooting:
  Configuration Info
  The current configuration is loaded from: /Users/daust/oc-jasper
  Config-Directory: /Users/daust/oc-jasper/conf
  Config-File:/Users/daust/oc-jasper/conf/application.properties
  Reports-Directory:/Users/daust/oc-jasper/reports
  Temp-Directory:/Users/daust/Dropbox/Programme-Mac/eclipse-workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/JasperReportsIntegration-EclipseTest/report_tmp
  Logs-Directory:/Users/daust/oc-jasper/logs
  Java-Runtime-Version:1.6.0_65
  JasperReports-Version:6.1.1

- FEATURE: #299 - Changed implementation for format "html": deprecated JRHtmlExporter replaced with HtmlExporter

- This is related to the upgrade to the newer JasperReports APIs (FEATURE: #675), the architecture has changed in the recent years. Now there is no longer a difference in the format "html" and "html2", they both are implemented using the HtmlExporter ( http://jasperreports.sourceforge.net/api/net/sf/jasperreports/engine/export/HtmlExporter.html )

- FEATURE: #300 - Upgrade from JDK 1.4 to JDK 1.6

- The minimum requirement for the J2EE application is now a Java Runtime with at least JRE version 6.

- FEATURE: #673 - Upgrade to JasperReports version 6.1.1

- The embedded JasperReports libraries have been updated to version 6.1.1.

- FEATURE: #674 - Security: Change Test Application - user objects are no longer displayed

- The test application used to display all user objects in the schema of the connected data source. This is changed and will display less details:

Session User | Parsing User | Instance Name | DB Name | Server Host | Current Time
--- | --- | --- | --- | --- | ---
TEST | TEST | XE | XE | dev-min | 05.10.2015 10:08:30

- FEATURE: #675 - Update API calls (some are deprecated)

- The architecture of JasperReports has changed over the years. Although the "old" APIs still worked ... they were nevertheless deprecated already for a long time. Thus it was about time to use the newer API calls in order to move forward and still be compatible with the newer versions for the future. But thas was a major (internal) rewrite.

- FEATURE: #676 - Resolve local files with relative file paths, i.e. images in the same directory as the report itself

- This was often a bummer, but now it works as expected. You don't need the workaround any longer: http://daust.blogspot.de/2014/04/jasperreportsintegration-full-path.html
- I guess this will not only affect the usage of local images in the filesystem but also references to subreports. Should make the deployment a lot simpler and less error prone.

- FEATURE: #678 - Security: Encrypt password in application.properties file

- You can now encrypt the password in the application.properties file on the command line.

- FEATURE: #680 - Security: Move default folder to WEB-INF

- The folders conf, reports and logs were moved to the WEB-INF subdirectory. There they are not accessible from the outside and better protected. Nevertheless, this was only an issue for those people who didn't

- FEATURE: #684 - Security: disable j2ee info and test page (as a configurable parameter)

- The homepage of the J2EE application can be disabled using a parameter in application.properties file:

- #====================================================================
  # Application properties (global)
  #====================================================================
  [application]
  configFileVersion=2.3.0
  jndiPrefix=java:comp/env/jdbc/
  # infoPageIsEnabled will show the initial start page of the j2ee application
  # including testing and the environment settings
  infoPageIsEnabled=false

- FEATURE: #689 - Set initial log level to INFO for classes de.oc.* from ALL
- FEATURE: #692 - Setup-script to change the setting for the config-directory in the JasperReportsIntegration.war file

- The configuration directory (including conf, reports and logs) can be set either using the environment variable OC_JASPER_CONFIG_HOME but also specifically for each J2EE application individually. This typically requires to extract the file web.xml from .war file, manipulate the file and put it all together again.
- Now you can just set a new directory path for the .war file on the command line and the web.xml file will be manipulated accordingly.

### Version 2.1.0.0 13.05.2013

- 2.1.0: REQ-00025 (SYSTEM): Support for JasperReports 5.1.0
- 2.1.0: REQ-00026 (SYSTEM): Add configuration of web.xml parameter for location of config files
- 2.1.0: REQ-00028 (SYSTEM): html2 format for using the new HTMLExporter in JasperReports 5.0
- 2.1.0: REQ-00030 (CHANGE): tunnel images for html reports through the database

### Version 2.0.0.0 (BETA release) / 05.08.2012

- Support for JasperReports 4.7.0

- The new libraries have been included. But you can also update the libraries separately.

- Included Oracle JDBC connection pool

- In addition to the JNDI data sources (which have to be configured differently for each J2EE server) you can use plain Oracle JDBC connections out of the box. A configuration file is available and the required Oracle drivers are already included.

- Easy deployment on different J2EE servers: Tomcat, Glassfish, Weblogic
- Quick start

- Easy getting started with included Jetty J2EE server, no need to configure a different J2EE server, perfect for development / testing.

- Support for direct printing
- Support for saving files on the server
- In case of an error, the mime-type will be changed to plain/text

- Previously you would get a pdf document returned in which the text error message was included.

- Major refactoring of the code

- has been instrumented with log4j messages in order to allow fine grained logging.

### Version 1.3.0.2 / 08.07.2012

- Support for JasperReports 4.6.0, the new libraries have been included. But you can also update the libraries separately

### Version 1.3.0.1 / 08.03.2012

- Bugfix when resolving the datasource. The simple test works but not the generation of reports.
- To upgrade, either install the new version 1.3.0.1 completely or just replace the file JasperReportsIntegration-1.3.0.0.jar with the newer file JasperReportsIntegration-1.3.0.1.jar in the directory %TOMCAT_HOME%/webapps/JasperReportsIntegration/WEB-INF/lib

### Version 1.3.0.0 / 19.12.2011

- Upgrade of the libraries to Jasper Reports 4.5.0.
- Support added to upgrade the Jasper Reports libraries later separately from the base install.

### Version 1.2.0.5 / published on 29.03.2011

- Upgrade of the libraries to Jasper Reports 4.0.0.
- Hard coded property settings for all report types are removed
  - "jasperreports.properties" is loaded from classpath if found
  - Properties are loaded from report directly if set
- Xlsx (MS Excel 2003) support added
- Docx (MS Word 2003) support added
- Pptx (MS Powerpoint 2003) support added

### Version 1.1.0.0 / published on 29.08.2010

- Upgrade of the libraries to Jasper Reports 3.7.4. Before, only reports created with iReport version 3.6.0 and below could have been run with this integration kit. Now the most up-to-date version of the JasperReports libraries are included.
- Instructions for using the integration on Oracle 11.x was added. In order to use http callouts one has to configure the access control lists (ACL) for accessing external network resources.

### Version 0.8.0.1 / published on 15.01.2010

- problem in the files sql/xlib_jasperreports/xlib_jasperreports.pks
  and sql/xlib_jasperreports/xlib_jasperreports.pkb
  The schema XLIB3 was hardcoded.
- removed the line from the configuration file context.xml (=> JasperReportsIntegration.xml)
  <!DOCTYPE web-app PUBLIC"-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
  "http://java.sun.com/dtd/web-app_2_3.dtd">
  Seemed to cause problems with one of the testers on Tomcat 6.0.18

### Version 0.8.0.0 / published on 14.01.2010

This is the first beta release.