riskop

No, I am not using custom fonts. The textual sections in the jrxml file looked like this: <textField> <reportElement x="0" y="0" width="120" height="20" uuid="43249a30-6a76-4c52-b89e-a0a6c6dd68d8"/> <box leftPadding="3" rightPadding="3"/> <textElement textAlignment="Left" verticalAlignment="Middle"> <font pdfFontName="Helvetica" pdfEncoding="Cp1250" isPdfEmbedded="true"/> </textElement> <textFieldExpression><![CDATA[$F{createdDate}]]></textFieldExpression> </textField> as far as I know <font pdfFontName="Helvetica" pdfEncoding="Cp1250" isPdfEmbedded="true"/> means that "Helvetica" font is used which is supplied by the environment (OS) via the JRE. And that is the problem because the OS provides different "Helvetica" fonts on different servers. If I change that to <font fontName="DejaVu Sans" fontSize="12" pdfEncoding="Cp1250" isPdfEmbedded="true"/> then the PDF size grows a bit which I think is the result of *really* embedding the DejaVu font in the pdf. The font looks a little bit different also on the PDF. But I think this is the "bulletproof" way of generating the PDF: the DejaVu font is coming from the "jasperreports-fonts" artifact which is bundled in the .war file, and the DejaVu font is embedded into the PDF. I read this doc: https://jasperreports.sourceforge.net/sample.reference/fonts/

I have a Spring Boot web application which generates pdf files based on jrxml templates. On certain servers the generated pdfs contains chopped of texts. On other servers the generated pdfs are OK. Everything is contained in the war, there are no external libraries used by the app. Do you have any idea what can cause this? This is the OK pdf: This is the chopped of pdf:

Hello, We created a QueryExecuter for executing multiple SQL queries. This executer can utilize for example the following query string (mysql): " create temporary table temp as select age,count(*) as groupSize from user group by age; select groupSize, max(age) from temp group by groupSize " For that we modified the createStatement() method of JRJdbcQueryExecuter. But we couldn't test the following portion of the code (lines 178-181, version 1719): if (queryParameter.isMulti()) { paramIdx += setStatementMultiParameters(paramIdx, queryParameter.getName()); } Could you point us an example which utilizes this branch of code (multiParameters howto?) ? Thanks, Peter