[
https://issues.apache.org/jira/browse/PDFBOX-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Lehmkühler resolved PDFBOX-257.
---------------------------------------
Resolution: Fixed
Fix Version/s: 1.3.0
The patch was already added in the past. Set to resolved.
> PDFMergerUtility may create non-unique AcroForm field names
> -----------------------------------------------------------
>
> Key: PDFBOX-257
> URL: https://issues.apache.org/jira/browse/PDFBOX-257
> Project: PDFBox
> Issue Type: Bug
> Components: PDModel.AcroForm
> Priority: Minor
> Fix For: 1.3.0
>
> Attachments: PDFMergerUtility.diff
>
>
> [imported from SourceForge]
> http://sourceforge.net/tracker/index.php?group_id=78314&atid=552832&aid=1682230
> Originally submitted by jochen-seifarth on 2007-03-16 08:46.
> org.pdfbox.util.PDFMergerUtility may in may cases create non-unique field
> names.
> Field names that already exist are replaced with "dummyFieldName" +
> sequenetial number. However, there is no check if that field name (i.e.
> "dummyFieldName" + sequenetial number)already exists. When executing several
> merges with different instances of PDFMergerUtility that each have their own
> counters there may be a collision of names causing chaos on merged forms.
> Attached is a patch that should guarantee to pick a unique field name.
> [attachment on SourceForge]
> http://sourceforge.net/tracker/download.php?group_id=78314&atid=552832&aid=1682230&file_id=220893
> PDFMergerUtility.diff (application/octet-stream), 1207 bytes
> PDFMergerUtility.java diff against HEAD
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
