Apache Camel FOP Component Not Propagating Headers

Question

The FOP component doesn't appear to be propagating headers. In the route below, headers are available to the XSLT component and it does pass them through the other side. But after fop, they're all gone.

Is this a bug?. Can someone suggest a workaround?

<route>
    <from uri="direct:render"/>
    <to uri="xslt:file:{{rootDir}}/Report.xsl"/>
    <to uri="fop:application/pdf"/>
    <log message="Headers after fop ${headers}"/>
</route>

thanks

score 0 · Accepted Answer · answered Apr 12 '13 at 18:57

OK, my workaround is as follows:

<route>
    <from uri="direct:render"/>

    <!-- Retain header value in property before it's lost -->
    <setProperty propertyName="lostHeader">
        <simple>${header.lostHeader}</simple>
    </setProperty>

    <to uri="xslt:file:{{rootDir}}/Report.xsl"/>
    <to uri="fop:application/pdf"/>

    <!-- Restore it again -->
    <setHeader headerName="lostHeader">
        <simple>${property.lostHeader}</simple>
    </setHeader>

    <log message="Headers after fop ${headers}"/>

    <!-- Now it's available again here -->
    <to uri="jms:jms/happyQueue"/>
</route>

As I said, it's a workaround and, of course, you'd have to handle any headers you need individually. I will probably log a jira bug on the fop component.

Yeah seems like a bug. Please feel free to log a JIRA ticket at: http://camel.apache.org/support — Claus Ibsen, Apr 14 '13 at 08:49
I logged a ticket so we will remember to fix it: https://issues.apache.org/jira/browse/CAMEL-6284 — Claus Ibsen, Apr 15 '13 at 16:31

Apache Camel FOP Component Not Propagating Headers

1 Answers1