It would be easier if you raised a ticket. You would be able to upload your project files as well.
From: Jörn Willhöft <j...@willhoeft-it.com> Sent: Thursday, November 7, 2024 9:49 AM To: fop-users@xmlgraphics.apache.org Subject: RE: Namespaces are dropped in XMP stream. XML invalid You don't often get email from j...@willhoeft-it.com<mailto:j...@willhoeft-it.com>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> Well the bug is in Apache FOP (or maybe in Saxon?) Here is a reproducible test procedure: I use the FOP binary package from https://www.apache.org/dyn/closer.cgi?filename=/xmlgraphics/fop/binaries/fop-2.10-bin.tar.gz&action=download and the current Saxon 12.5 HE. Create PDF without Saxon: $ fop-2.10/fop/fop -c PDFA3Xmp.xconf -fo PDFXMP.fo -pdf output-ok.pdf Create PDF with Saxon: $ export CLASSPATH=SaxonHE12-5J/saxon-he-12.5.jar:SaxonHE12-5J/lib/xmlresolver-5.2.2.jar:SaxonHE12-5J/lib/xmlresolver-5.2.2-data.jar:SaxonHE12-5J/lib/jline-2.14.6.jar $ fop-2.10/fop/fop -c PDFA3Xmp.xconf -fo PDFXMP.fo -pdf output-saxon.pdf Result without Saxon: $ pdfinfo -meta output-ok.pdf ... <rdf:Description xmlns:pdfaExtension="http://www.aiim.org/pdfa/ns/extension/"; rdf:about=""> <pdfaExtension:schemas> <rdf:Bag> <rdf:li rdf:parseType="Resource"> <pdfaSchema:property xmlns:pdfaSchema="http://www.aiim.org/pdfa/ns/schema#";> <rdf:Seq> <rdf:li rdf:parseType="Resource"> <pdfaProperty:name xmlns:pdfaProperty="http://www.aiim.org/pdfa/ns/property#";>split</pdfaProperty:name> </rdf:li> </rdf:Seq> </pdfaSchema:property> </rdf:li> </rdf:Bag> </pdfaExtension:schemas> </rdf:Description> ... The result with Saxon is totally messed up: $ pdfinfo -meta output-saxon.pdf ... <rdf:RDF xmlns:pdfaExtension="http://www.aiim.org/pdfa/ns/extension/"; rdf:about=""> <pdfaExtension:schemas> <rdf:Bag> <rdf:li rdf:parseType="Resource"> <pdfaSchema:property> <rdf:Seq> <rdf:li rdf:parseType="Resource"> <pdfaProperty:name>split</pdfaProperty:name> </rdf:li> </rdf:Seq> </pdfaSchema:property> </rdf:li> </rdf:Bag> </pdfaExtension:schemas> </rdf:RDF> ... Not only the namespace attributes xmlns:pdfaSchema and xmlns:pdfaProperty are missing, but also the rdf:Description element is now called rdf:RDF (?!) I think it makes sense to create a Jira ticket for this issue. Since I am not a member of the project, shall I sign up and do this? Cheers Jörn Willhöft Jörn Willhöft <j...@willhoeft-it.com<mailto:j...@willhoeft-it.com>> hat am 07.11.2024 13:34 CET geschrieben: OK, I am a big step further now. The bug appears in Camel (only) if Saxon is used anywhere in the Camel Route. I use Saxon to create the actual FO and additional files. The created FO has the namespaces where they belong, but somehow Saxon in the classpath seems to confuse the FOP component internally. Skipping Saxon is not really an option as I need XSLT 2.0. It is still unclear to me if the problem is in the Camel FOP component or FOP itself. Cheers Jörn Willhöft ________________________________ Joao Andre Goncalves Customer Developer t | m 07733161880 jgoncal...@smartcommunications.com smartcommunications.com<https://www.smartcommunications.com/> [https://scale.smartcommunications.com/rs/041-BQO-927/images/024_Esignature-2024-Benchmark.png?version=0]<https://www.smartcommunications.com/resources/benchmark-report/?utm_source=outlook&utm_medium=email&utm_campaign=benchmark_report_2024_webpage> The largest study of its kind! Unlock unparalleled insights into customer preferences and stay ahead in today's market. Download now!<https://www.smartcommunications.com/resources/benchmark-report/?utm_source=outlook&utm_medium=email&utm_campaign=benchmark_report_2024_webpage> Smart Communications is a trading name of SmartComms SC Limited which is registered in England under No. 4303041 whose registered office is at Suite 23, LCLB, 95 Mortimer Street, London, W1W 7GB. Please consider the environment before printing. The contents of this e-mail are intended for the named addressee only. It contains confidential information. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. Smart Communications will process your data as described in the Smart Communications' External Privacy Policy.<https://www.smartcommunications.com/external-privacy-policy/> Follow us on LinkedIn<https://www.linkedin.com/company/15166060/admin/> and Twitter<https://twitter.com/ccminnovators?lang=en>
