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
