Michael, you give me the clue.
Indeed the problem would be solved by adding a human readable description
in the anottation, i.e, the signature filed.
Add in the preClose method of PDFSignatureAppearance somethig like :
sigField.put(PdfName.CONTENTS, new PdfString("some text",
PdfObject.TEXT_UNICODE));
But now, i've on the way of how to implement in my code your workaround
Thanks!
*Jose*
2014-10-24 15:52 GMT+02:00 Jose Mª Viota <josemav...@gmail.com>:
> Thanks Michael,
> I'll get right on it.
>
> *Jose*
>
> 2014-10-24 15:18 GMT+02:00 mkl <m...@wir-sind-cool.org>:
>
>> Jose,
>>
>> Jose Mª Viota wrote
>> > Both of Adobe Reader and Adobe Pro verifies the conformance but iText
>> says
>> > me that "Annotation of type /Widget should have Contents key"
>>
>> First of all the message says SHOULD. If the wording is RFC'ish, this
>> means
>> that this merely refers to a recommendation of the PDF/A specification,
>> not
>> a requirement, so there may *exist valid reasons in particular
>> circumstances
>> to ignore* it.
>>
>> Third-party conformance checkers do not know whether in such a case valid
>> reasons existed. They, therefore, may not fail verification if merely a
>> recommendation is not heeded.
>>
>> PDF generators may be stricter in this respect and enforce
>> recommendations.
>>
>> In the case at hand we are talking about the recommendation to include a
>> Contents entry in an Annot dictionary "for Level A conformance of
>> non-textual annotations":
>>
>> > For annotation types that do not display text, the Contents key of an
>> > annotation dictionary should be specified with an alternative
>> description
>> > of the annotation's contents in human-readable form.
>>
>> In the PDF at hand the annotation is a signature field widget annotation,
>> and a digital signature not necessarily displays text. Thus, one can
>> indeed
>> argue that this recommendation should be heeded.
>>
>> That all been said, it is somewhat funny that iText itself (in
>> PdfSignatureAppearance.preClose) creates this annotation it finds
>> lacking...
>> it does not live up to its own requirements. ;)
>>
>> To get around this you might want to try a two-pass approach; in the first
>> pass you create an empty signature field which you enhance with a Contents
>> annotation and then add to the document, and in the second pass you sign
>> using this empty signature field.
>>
>> Regards, Michael
>>
>>
>>
>> --
>> View this message in context:
>> http://itext-general.2136553.n4.nabble.com/Java-iText-Error-while-check-pdf-PDF-A-1A-tp4660479p4660494.html
>> Sent from the iText - General mailing list archive at Nabble.com.
>>
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> iText-questions mailing list
>> iText-questions@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/itext-questions
>>
>> iText(R) is a registered trademark of 1T3XT BVBA.
>> Many questions posted to this list can (and will) be answered with a
>> reference to the iText book: http://www.itextpdf.com/book/
>> Please check the keywords list before you ask for examples:
>> http://itextpdf.com/themes/keywords.php
>>
>
>
------------------------------------------------------------------------------
_______________________________________________
iText-questions mailing list
iText-questions@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/itext-questions
iText(R) is a registered trademark of 1T3XT BVBA.
Many questions posted to this list can (and will) be answered with a reference
to the iText book: http://www.itextpdf.com/book/
Please check the keywords list before you ask for examples:
http://itextpdf.com/themes/keywords.php
