[
https://issues.apache.org/jira/browse/CAMEL-17048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-17048:
--------------------------------
Summary: Exchange header null after upgrading to 3.12 from 3.11.2 when
using transacted (was: Exchange header null after upgrading to 3.12 from
3.11.2)
> Exchange header null after upgrading to 3.12 from 3.11.2 when using transacted
> ------------------------------------------------------------------------------
>
> Key: CAMEL-17048
> URL: https://issues.apache.org/jira/browse/CAMEL-17048
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 3.12.0
> Reporter: Andre
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 3.13.0
>
>
> After upgrading camel from {{3.11.2}} to {{3.12.0}} I notice that a header I
> set in a processor is not being available "later on" anymore.
> h5. It looks as follows:
> Route
> {noformat}
> from(source)
> .process(myprocessor::setHeader)
> ...
> .process(anotherprocessor)
> ..
> .to(target)
> ;
> {noformat}
> where myprocessor.setHeader does sth like
> {noformat}
> void setHeader(Exchange exchange) {
> exchange.getIn().setHeader("my-header", 1234);
> }
> {noformat}
> and {{anotherprocessor}} wants to access this header, e.g.
> {noformat}
> @Override
> void process(Exchange exchange) {
> ...
> Long value = exchange.getIn().getHeader("my-header", Long.class);
> if (value == null) {
> throw ..
> }
> }
> {noformat}
> While with 3.11.x this works fine it stopped with 3.12.0.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
