We are creating PDF/X 2B documents and want to do so with Jasper. This works fine, but our customers are allowed to upload images for these reports. One problem arises when these images have transparency, which will lead to
PdfXConformanceException: The /SMask key is not allowed in images.
when we try to convince Jasper to create an PDF/X document with:
SimplePdfExporterConfiguration exportConf = new SimplePdfExporterConfiguration();
This exception is useless to us because PDF/A 2x ALLOW transparent images. I would love to have the additional PdfaConformanceEnum values PDFA_2B (and maybe PDFA_2A) which shouldn't differ from PDFA_1B or PDFA_1A in regard to Jasper to just skip that SMask check. And of course in regard of the constant to be stored in the generated document that designates the PDF/a version.