Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Jason Sanders (JasonS52) Coforge Limited Senior System Analyst
Coforge Limited
US
JasonS52 Member since 2017 1 post
Coforge Limited
Posted: Mar 26, 2020
Last activity: May 27, 2020
Posted: 26 Mar 2020 9:54 EDT
Last activity: 27 May 2020 1:33 EDT
Closed

Issues Converting .docx To .pdf With DocX4J 6.1.1

Hello everyone,

A few months ago, I implemented an Activity that used the DocX4J library that comes with Pega 8.1.4 as well as the PDFBox library that has been available since Pega 7.3.1.

The code inside the Java Step is intended to convert an attachment of .docx format into .pdf format before appending it to an existing PDF. I do this by taking the bytes of both the existing PDF and the .docx attachment, using DocX4J to convert the .docx bytes into .pdf bytes, then using PDFBox to merge the new PDF bytes into the existing PDF bytes. I have included a text file showing the exact lines used.

Recently, this functionality has stopped working. Checking the logs shows that DocX4JExceptions are being thrown. I have attached a second text file with a copy of the stack trace associated with this exception.

Has anyone successfully implemented this functionality in the past with Pega 8.1.4/DocX4J 6.1.1? Any insight as to what's gone wrong and how to fix it would be greatly appreciated.

To see attachments, please log in.
Pega Platform 8.1.4 Dev/Designer Studio Senior System Architect

Posted: 4 years ago
Posted: 2 Apr 2020 10:00 EDT
Jason Sanders (JasonS52) Coforge Limited Senior System Analyst
Coforge Limited
US

Further investigation has led me to believe this is an issue with Pega 8.1.4's implementation of DocX4J. Going off the stack trace, we can find that the issue has something to do with the ObfuscatedFontPart class's tmpFontDir variable being initialized as null.

I've run diagnostics in our Pega environment, and this "tmpFontDir" variable is pointing towards a file located in "/home/tomcat/.docx4all/temporary embedded fonts." This filepath is likely not a valid one, which is why the tmpFontDir file is unable to be located and thus throws the resulting error.

Can anyone provide insight as far as where to go from here? I've filed a support ticket with Pega through MSP, and will update this thread once more if and when a solution is implemented successfully.

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice