tcleenewerck

The onErrorType attribute of the image element is applicable only to errors that occur during the loading of images from files or input streams. It does not cover errors raised by the image expression at evaluation time. Data providers should behave as a database: when data (in this case an image) is requested, it should not fail but simply respond with an image or null. However as it is possible to write complex expression, it would be useful to trap errors during image expression evaluation as well. Upon request, a bugreport for this has been submitted: http://community.jaspersoft.com/jasperreports-library/issues/9156. Thank you Teodor and Lucian for looking into this.

I'm currently using library 6.2.0. We have implemented our own provider. The provider produces images which we can retrieve using a certain expression. ..getScaledImageFieldValue(...) The signature of the method that we call to rettrieve the image is: public BufferedImage getScaledImageFieldValue(String fieldname, int maxWidth, int maxHeight) throws JRException { The JRException is not caught when we fail to retrieve the image for example due to a network break-down.

We had to implement our own function to fetch images because we need to manipulate them before we give them to the Jasper report library. However in case some error occurs we throw a JRException. Although the onErrorType attribute on the image component is set to "Blank" the generation of our report fails. It seems that a JRException is not captured and recognised as an error. As a result the exception propagates and breaks the generation of the report. We've tried to used other types of exceptions such as IOException but that doesn't seem to work as well. What kind of errors (java exception or something else) are catched so that the report generation succeeds and that the image is left blank as expected. Looking forward for some help Thomas

Hello Teodor Please take a moment to respond to our question above. We just need some information in order to proceed. Thomas

Hello Teodor There multiple sub issues here. Please advise on both of them. 1/ The redirect doesn't entiry work with JR 6.3.0. Version 6.3.1 is not available in my studio, so I cannot test it. To illustrate this try the following report named 'redirect.jrxml'. We used the report in our test suite. 2/ Anyhow we had to implement our own function to fetch images because we need to manipulate them before we give them to the Jasper report library. However in case some error occurs we throw a JRException. Although the onErrorType attribute is set to "Blank" the generation of our report fails. It seems that a JRException is not captured and recognised as an error. As a result the exception propagates and breaks the generation of the report. We've tried to used other types of exceptions such as IOException but that doesn't seem to work as well. Could you advise us what kind of errors (java exception or something else) are catched so that the report generation succeeds and that the image is left blank as expected. Best regards Thomas

Dear Teodor I'm a colleague of Maarten and I would like to join in on this issue. We are grateful that you guys are looking to support redirects.Meanwhile and until the issue of a redirect is supported natively, we have implemented our own java function to follow the redirects and retrieve our images. However in case the url is flawed (e.g. it yields status code 404 for example) we throw a JRException. Although the onErrorType attribute is set to "Blank" the generation of the report fails. It seems that a JRException is not captured and recognised as an error. As a result the exception propagates and breaks the generation of the report. We've tried to used other types of exceptions such as IOException but that doesn't seem to work as well. Could you advise us what kind of errors (java exception or something else) are catched so that the report generation succeeds and that the image is left blank as expected. Best regards Thomas

When a list component is set to print horizontally and the amount of data to be printed is bigger than the page width than the contents is simply cut of. In other words, the list doesn't continue printing on the next line. Code: Post Edited by tcleenewerck at 01/19/2012 10:08