[ https://issues.apache.org/jira/browse/PDFBOX-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14245417#comment-14245417 ]
Ralf Hauser commented on PDFBOX-2562: ------------------------------------- re 2) suggestion i) create a class ValidationItem that is almost identical to today's ValidationError ii) subclass ValidationError from ValidationItem iii) subclass ValidationWarning from ValidationItem iv) in ValidationResult.java add private List<ValidationWarning > lWarnings v) create addValidationWarning() methods in PreflightContext and PreflightDocument vi) now specific for the CCITT problem: in ResourcesValidationProcess.validateXObjects(), in the IOExeption catch block, make it a ValidationWarning > create ValidationWarnings > ------------------------- > > Key: PDFBOX-2562 > URL: https://issues.apache.org/jira/browse/PDFBOX-2562 > Project: PDFBox > Issue Type: Sub-task > Components: Preflight > Affects Versions: 2.0.0 > Reporter: Ralf Hauser > Priority: Minor > Fix For: 2.1.0 > > > as seen in the parent Issue PDFBOX-2513 , pdf/A1 is not required to validate > other standards like TIFF completely. > On the other hand, the information from the CCITTFaxDecoder is valuable and > shouldn't be simply discarded. > Therefore, I suggest that this information is displayed without setting the > validation result to false. > ValidationWarnings could have the same logical structure as ValidationError . -- This message was sent by Atlassian JIRA (v6.3.4#6332)