You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pdfbox.apache.org by "Tilman Hausherr (JIRA)" <ji...@apache.org> on 2016/12/01 17:35:58 UTC
[jira] [Closed] (PDFBOX-3613) FDFField creates wrong object type,
when loaded from XML
[ https://issues.apache.org/jira/browse/PDFBOX-3613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tilman Hausherr closed PDFBOX-3613.
-----------------------------------
Resolution: Duplicate
Duplicate of PDFBOX-3596, I've added you as a watcher there. I think my own patch is better because it comes later. However yours and mine are both not enough, see discussion there.
> FDFField creates wrong object type, when loaded from XML
> --------------------------------------------------------
>
> Key: PDFBOX-3613
> URL: https://issues.apache.org/jira/browse/PDFBOX-3613
> Project: PDFBox
> Issue Type: Bug
> Components: AcroForm
> Affects Versions: 2.0.3
> Reporter: Bernd Engelhardt
> Attachments: FDF_Import.patch
>
>
> When a FDFDocument is loaded from file with
> {code}
> FDFDocument fdfDocument = FDFDocument.loadXFDF(is)
> {code}
> and afterwards the same documet is saved via
> {code}
> fdfDocument.saveXFDF(...)
> {code}
> the output document contains only empty fields. The problem is that
> {code}
> FDFField(Element fieldXML)
> {code}
> creates with "setValue" not a "COSString", what is expected by "getValue", when saving the document.
> FDFField should use
> {code}
> setValue(new COSString(XMLUtil.getNodeValue(child)));
> {code}
> to create correct values for the XML nodes. Otherwise the import of FDF documents via e.g.
> {code}
> pdAcroForm.importFDF
> {code}
> does not work correct.
> Patch for 2.0.3 is attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
For additional commands, e-mail: dev-help@pdfbox.apache.org