Sounds like the PDF is broken. For further investigation you would have to
post your PDF
2013/8/2 Josh Smith
> The system writes the output file to disk. If I take a separate set of
> code and read in the file before an after population ( both off disk) the
> populated form doesn't have a
The system writes the output file to disk. If I take a separate set of
code and read in the file before an after population ( both off disk) the
populated form doesn't have any fields in its AcroForm collection.
Sent from my iPhone
On Aug 2, 2013, at 1:03 PM, TvT wrote:
>I take the form aft
>I take the form after it's been populated by iText, if I call for it's
AcroForm, I get back a null.
Do you close the stamper and read the document again? And then its null?
That would be indeed weird.
So try the following - re-read the file you filled with iText from your
localdisk and get the ac
It does seem to work before It goes through iText.
I am setting the fields like this.
PdfStamper stamp = new PdfStamper(
new PdfReader(templateBody), output, '\0');
AcroFields form = stamp.getAcroFields();
for (String key : form.getFields().keySet()) {
if (dataLoa
then there are two questions:
- does the document works before you put it through iText?
- How do you populate (=fill) its textfields?
2013/8/2 Josh Smith
> These are textfields.
> They are not grouped in a hierarchy. All fields reside at the same level.
>
> In doing some more digging, I notic
These are textfields.
They are not grouped in a hierarchy. All fields reside at the same level.
In doing some more digging, I noticed that when I take the form after it's been
populated by iText, if I call for it's AcroForm, I get back a null. But before
iText processing, the AcroForm can be c
With the functionality you describe do you mean autofill? So you fill one
field and the others with the same name are automatically filled with the
same content?
I just tried a pdf of mine and it is working fine in chrome. I can now only
think that chrome has a problem with a certain characteristi
Op 2/08/2013 11:43, Josh Smith schreef:
> Unfortunately I don't have control of the end users computers to
> enforce that on everyone.
> I know its nit an iText issue but is there so change I can make via
> iText to the output to work around this?
The only workaround is to change the form. Instead
Unfortunately I don't have control of the end users computers to
enforce that on everyone.
I know its nit an iText issue but is there so change I can make via
iText to the output to work around this?
Sent from my iPhone
On Aug 2, 2013, at 2:54 AM, iText Info wrote:
> Op 1/08/2013 21:50, jesmith
Op 1/08/2013 21:50, jesmith schreef:
> they are also
> displayed if I view the PDF in true client app (Mac Preview, or Adbobe
> Reader).
If Adobe Reader displays them and even Mac Preview displays them, but
not Chrome PDF Viewer (and probably not pdf.js in Firefox either), then
you're facing a pr
10 matches
Mail list logo
