Step 1: Download the files for 5.0.1

Step 2: Shutdown the Apache Tomcat J2EE server

Typically, after you have installed your previous version of the JasperReportsIntegration toolkit on your Apache Tomcat J2EE server, the files will be located in the directory $CATALINA_HOME/webapps/JasperReportsIntegration/WEB-INF/lib, for example version 4.7.0 of JasperReports, where $CATALINA_HOME represents the path to your installation of Tomcat.

Then you would have to remove these libraries first. In this directory you should find two files for removal: _jasper-reports-delete-libs-4.7.0.sh and _jasper-reports-delete-libs-4.7.0.cmd, for *nix or Windows respectively. For *nix systems you would have to make it executable, though, e.g.: chmod u+x _jasper-reports-delete-libs-4.7.0.sh . Then you can call it and it will remove all files for version 4.7.0. But it will NOT remove the file for the JasperReportsIntegration and all other libraries which YOU might have placed there deliberately.

Dietmar, i do appreciate You for Your support of product. I've successfully upgraded to 5 1 0. By the way, it seems work stable with Jaspersoft Studio 5 1 0. I have not overall tested of course, but results are helpful ;)

>"tunnel images for html reports through the database".Sure. Most people were using the integration for producing PDF, MS Word or MS Excel. For these purposes a request to xlib_jasperreports would call the J2EE server using utl_http.

If you want to generate HTML it works a bit differently. The first call to xlib_jasperreports will return the html page with the report to the client browser. All referenced images (even the px spacer image) need an URL to point back to the J2EE server.

For security reasons I want to prohibit all direct access to the J2EE server and allow only the database to talk to the J2EE directly. Thus I have to "tunnel" all image requests through the database to the J2EE server. In effect, the database works as a proxy to the J2EE server for all requests.

Here You are my modest first look report. I undeployed JRI war, deployed new one, edited just an application.properties about JDBC, removed apex application, run user_remove.sql, run user_install.sql, installed apex application. First look says that everything works okay, as always. I plan to kick JRI by means of ab.exe utility from apache distributive and will let You know about results.From my modest opinion You may advice JasperStudio in Your docs. I didn't tested a complex reports of course , but as i can see that product is in main stream of Jasper development.

Some issues appeared also.

1. user_remove leaves TYPE xlib_vc2_array_t so next run of user_install fails.

2. Some warnings present in user_install.log:*** grant xlib_jasperreports_img to publicSP2-0310: unable to open file "_grants.sql"~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~