Hi Tilman I have absolutely no idea. Today, I ran my tool over thousands of PDFs to migrate the form fields, and in the output log (created by redirecting stderr and stdout into a log file) I saw entries with "null", which do not come from my code ;). I have no means to reproduce it, since I had to run my tool in a high secure environment, but it seems that something with those PDFs, which I never had the chance to test, does not seem to work, and the only feedback I get from PDFBox is a line which reads "null".
Unfortunately, I have absolutely no idea which PDFs they are and I can't easily modify my tool and then re-run it again. This requires a complicated process. I will try to prepare as much useful output as possible for the next run (maybe on Monday) to hopefully pinpoint this down to the culprit. I just thought that meanwhile I'd ask if anyone ever encountered this before. Thanks for your time in answering my vague question. BTW: The tool, which you helped develop as well quite a bit with your great feedback has worked surprisingly well in its maiden run on the client side, especially since we only received a very small set of PDFs to test with. Ever since I introduced the Javascript injection code for the "document/open" event plus the setNeedAppearance(true), things sail smoothly. Logically, it will only work for Adobe products, but they do not have anything else. Best regards Roberto On Fri, Jul 31, 2015 at 6:35 PM, Tilman Hausherr <[email protected]> wrote: > Am 31.07.2015 um 15:46 schrieb Roberto Nibali: > >> Hi >> >> What could be the reason for PDFBox to simply reply "null"? >> > What do you mean with "reply" - as a console output, as a log output, or > as return value from a call? If it is a call, which one? > > > Tilman > > > >> I sporadically get such a reply from the library, but the processing just >> continues. I have absolutely no clue where this is generated. >> >> Best regards >> Roberto >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
