[ 
https://issues.apache.org/jira/browse/PDFBOX-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15450072#comment-15450072
 ] 

Rees Byars commented on PDFBOX-3218:
------------------------------------

This issue has been stagnant for a while. Bringing back to the top. If this 
issue can be addressed, it would be greatly appreciated. If any assistance is 
needed, please let me know.

Thank you. PDFBox is a killer library.

> PDFMergerUtility improperly merges AcroForms, causing some forms to break
> -------------------------------------------------------------------------
>
>                 Key: PDFBOX-3218
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-3218
>             Project: PDFBox
>          Issue Type: Bug
>          Components: Utilities
>    Affects Versions: 2.0.0
>            Reporter: Rees Byars
>            Assignee: Maruan Sahyoun
>         Attachments: PDFBOX-3218.patch
>
>
> In PDFMergerUtility.mergeAcroForm, adding a parent field to the destination 
> fields automatically adds the children, but the code does not account for 
> this. The result is that the same fields get added many times with different 
> names. This is a silent error for most PDFs. However, for some forms, the 
> resultant PDFs cause SOM expression errors in Adobe Reader. 
> This problem can be reproduced by appending the following PDFs in the order 
> listed:
> http://www.vba.va.gov/pubs/forms/VBA-21-4185-ARE.pdf
> http://www.vba.va.gov/pubs/forms/VBA-21-534EZ-ARE.pdf
> We were able to fix this issue for our purposes by forking the github mirror 
> and altering the mergeAcroForm method to only append fields whose parent is 
> null.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to