#26999

Hi,

We’ve been using PD4ML to generate JSPs within our application for some time without any problem.

We are now looking to upgrade our application server and are now using Glassfish 4 (from Glassfish 3) running on Java 8 (was Java 6) and now our PDFs are not generating – all we get is several blank pages and the spinning wheel as if its trying to load something.

We are running PD4ML 360fx1 and I have also tested version 385fx1 but get the same issue with the blank page.

I’ve looked in the console and we get the following from inside pdf.worker.js.
Warning: Unsupported feature “unknown”
Error: Bad encoding in flate stream

I couldn’t see anything relating to Java version when looking at the release notes for newer versions of PD4ML, but can anyone shed any light on what might be causing this issue? Has anyone else had this problem?

Thanks in advance,

Zeetha

#29687

All resolved now.

After a lot of trial and error, turned out that removing the tag:

<%@ page contentType="text/html;charset=iso-8859-15" %>

From the top of the js file was what was needed. PDF is now generating as expected.

Z

#27000

Hi there,
I have the following issue:
I use PD4ML tags library which gets a custom tag as a body of PDF. Additionally I use headers and footers also as a custom tags. So the umlauts ö,ü,ß working fine, but ä sometimes shows broken character (a?).
Could you please check it? It’s really interesting because in the same document could be valid and broken umlauts…
P.S. See attached example

#29689

Unfortunately you did not publish a JSP code snippet to see the way you defines headers/footers.

Try to define headers with HTML code using instead of (and footers correspondingly).

Does it change anything?

#29690

Nope.. The issue that header/footer shows the umlauts without any problems.. But body sometime fails with ä as I said.
The code looks like that:

<pd4ml:usettf from="java:fonts" serif="Times New Roman" sansserif="Arial" monospace="Courier New" /><br /> <pd4ml:page.header><br /> <t:pdf-header companyName="${companyName}" personName="${personName}" address="${companyAddress}" /><br /> </pd4ml:page.header><br /> <pd4ml:page.footer height="50"><br /> <t:pdf-footer partner="${invoice.partner}" /><br /> </pd4ml:page.footer><br /> <t:pdf-invoice invoice="${invoice}"><br /> <jsp:attribute name="title">${title}</jsp:attribute><br /> <jsp:body><br /> <table class="table padded"><br /> <tr class="header"><br /> <th width="10%" class="first"><spring:message code="pdf.finance.invoices.executionDate" /></th><br /> <th width="50%"><spring:message code="pdf.finance.invoices.product" /></th><br /> <th width="5%" class="text-right"><spring:message code="pdf.finance.invoices.quantity" /></th><br /> <th width="15%" class="text-right"><spring:message code="pdf.finance.invoices.pricePerItem" /></th><br /> <th width="10%" class="text-right"><spring:message code="pdf.finance.invoices.vat" /></th><br /> <th width="10%" class="text-right"><spring:message code="pdf.common.finance.amount" /></th><br /> </tr></table><br /> </jsp:body><br /> </t:pdf-invoice>

So inside <jsp:body> there are issues..

#29691

Hmm… Try to add enable=”false” to – it should return HTML instead of PDF. Check if all placeholders are substituted with data correctly. I would suspect some of them appear as ISO-8859-1, others as UTF-8 – encoded.

#29692

@PD4ML wrote:

Hmm… Try to add enable=”false” to – it should return HTML instead of PDF. Check if all placeholders are substituted with data correctly. I would suspect some of them appear as ISO-8859-1, others as UTF-8 – encoded.

Just checked the database data – everything stored as UTF..
With enable=”false” shows the valid values

#29693

Can you generate such HTML with a sensitive data stripped off and send it to support pd4ml com?

#29694

@PD4ML wrote:

Can you generate such HTML with a sensitive data stripped off and send it to support pd4ml com?

Done

#29695

A usual UTF-8 code for ä is “C3 A4”, in your document it is “61 CC 88” which is actually a separate definition for a and diacritical marks (umlaut dots) to be rendered as a single glyph.

I have found an explanation by the link http://www.redleopard.com/2008/12/character-codes-and-encoding/

Unfortunately PD4ML does not support that notation for the time being. So the only workaround is to replace “61 CC 88” byte chains with “C3 A4” or tune your database to return UNICODE data as regular UTF-8

#29679

It would help a lot if you published an exception stack trace and the source HTML, you passed to PD4ML (hopefully there is no sensitive data in it)

#29688

Glad you solved the issue!

#29676

Please send the relevant file(s) to support pd4ml com, and also please let us know which version of PD4ML you currently use.

#29675

OK – will send file to Support….

Here is the latest stack trace I received – seems to be ClassCastException related.

Merging : Address Changes 011410.pdf
Exception in thread “main” java.lang.ClassCastException: org.zefer.pd4ml.npdf.parser.obj.o cannot be cast to org.zefer.pd4ml.npdf.parser.obj.e
at org.zefer.pd4ml.npdf.parser.d.super(Unknown Source)
at org.zefer.pd4ml.npdf.parser.d.super(Unknown Source)
at org.zefer.pd4ml.npdf.parser.d.Ò00000(Unknown Source)
at org.zefer.pd4ml.npdf.parser.d.super(Unknown Source)
at org.zefer.pd4ml.npdf.parser.f.super(Unknown Source)
at org.zefer.pd4ml.npdf.parser.f.super(Unknown Source)
at org.zefer.pd4ml.npdf.parser.obj.h.o00000(Unknown Source)
at org.zefer.pd4ml.npdf.parser.obj.k.o00000(Unknown Source)
at org.zefer.pd4ml.npdf.parser.obj.h.o00000(Unknown Source)
at org.zefer.pd4ml.npdf.parser.obj.j.o00000(Unknown Source)
at org.zefer.pd4ml.npdf.parser.obj.k.o00000(Unknown Source)
at org.zefer.pd4ml.npdf.parser.obj.h.o00000(Unknown Source)
at org.zefer.pd4ml.npdf.parser.obj.k.o00000(Unknown Source)
at org.zefer.pd4ml.npdf.parser.g.super(Unknown Source)
at org.zefer.pd4ml.npdf.parser.g.super(Unknown Source)
at org.zefer.pd4ml.npdf.parser.g.super(Unknown Source)
at org.zefer.pd4ml.npdf.PD4DocumentBase.write(Unknown Source)
at org.zefer.pd4ml.npdf.PD4DocumentBase.write(Unknown Source)
at KmPrintBinder.MergePdfDoc2(KmPrintBinder.java:39)
at KmPrintBinder.MergePdfDocuments(KmPrintBinder.java:23)
at Pd4mlMergeDoc.main(Pd4mlMergeDoc.java:17)

#26998

Hello,

In the transformation to RTF for some reason some characters with accents are in Arial and others in Times New Roman when we specify that the font should be Arial, it is a bit random.
I attached both files, the html source and the generated file

Do you have any idea of why this is happening? any solution?

[Author]

Posts