[ 
https://issues.apache.org/jira/browse/CAMEL-4510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dragisa Krsmanovic updated CAMEL-4510:
--------------------------------------

    Description: 
In the simple example:

{code}
from("file:/foo.csv")
   .setHeader("MyHeader", constant("Hello"))
   .to("flatpack:foo");

from("flatpack:foo")
   .to("bean:importer");
{code}

Header "MyHeader" is not being passed to the bean in the second route.

Looking at Camel Flatpack code I see that in 
{{FixedLengthEndpoint.processDataSet}} it creates an exchange object from 
scratch and, thus, looses any incoming headers.

  was:
In the simple example:

{code}
from("file:/foo.csv")
   .setHeader("MyHeader", constant("Hello"))
   .to("flatpack:foo);

from("flatpack:foo")
   .to("bean:importer");
{code}

Header "MyHeader" is not being passed to the bean in the second route.

Looking at Camel Flatpack code I see that in 
{{FixedLengthEndpoint.processDataSet}} it creates an exchange object from 
scratch and, thus, looses any incoming headers.

    
> Camel flatpack component drops all headers from the original message
> --------------------------------------------------------------------
>
>                 Key: CAMEL-4510
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4510
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-flatpack
>    Affects Versions: 2.8.1
>            Reporter: Dragisa Krsmanovic
>              Labels: flatpack
>
> In the simple example:
> {code}
> from("file:/foo.csv")
>    .setHeader("MyHeader", constant("Hello"))
>    .to("flatpack:foo");
> from("flatpack:foo")
>    .to("bean:importer");
> {code}
> Header "MyHeader" is not being passed to the bean in the second route.
> Looking at Camel Flatpack code I see that in 
> {{FixedLengthEndpoint.processDataSet}} it creates an exchange object from 
> scratch and, thus, looses any incoming headers.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to