Skip to Content
Technical Articles
Author's profile photo Jigang Zhang 张吉刚

One easier way to deal with com.adobe.ProcessingException

This article is the successor of my previous blog ‘about System error at Adobe form processing‘ to deal with adobe form processing exceptions during a “Render” operation. The detail of this error message could be like below:

com.adobe.ProcessingException: com.adobe.ProcessingException: 0 : InvalidDataException: Xml parsing error: not well-formed (invalid token) (error code 4), line 1, column 16813 of file

(Note that the last part of this error is ‘column 16813 of file’. If we can get the original file then everything will be clear. But unfortunately, I couldn’t get this file directly. And no idea why so many columns are calculated~ Please let me know if it’s possible, thanks in advance!)

The most possible cause is some unique character like & < > ‘ ” inside the input parameters for the interface of adobe forms. Here is the way how to find this special character quickly.

1, Get the FM of the adobe form like ‘/1BCDWB/SM00000001’, where all input parameters have been used.

2, Go to FUNCTION ‘FPCOMP_FORM_END and set the break-point at FUNCTION ‘FPCOMP_CREATE_PDX’  in the routine ‘create_output_current_form’.

3, Print preview and trigger this adobe form output, and check the value of P_DOCUMENT-XFD in the HTML browser.

4, Copy all the contents and paste them into one word DOC file. (Txt file will not show this square~, and the output XML file will be truncated with default Fast Display).

5, Check the contents inside the HTML browser and trace back where this special symbol belongs to. For example using an item number or material number, qty, etc to decrease the searching scope. In my case, it’s the long text for one item.


Assigned Tags

      Be the first to leave a comment
      You must be Logged on to comment or reply to a post.