[
https://issues.apache.org/jira/browse/CAMEL-10343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15528540#comment-15528540
]
Andrea Cosentino commented on CAMEL-10343:
------------------------------------------
Hello Nicholas,
usually we use Github to open a Pull Request or alternatively you can create a
patch file add attach here that. How do you prefer.
Can you please do your modifications against the Apache Camel master branch?
Then we will backport the fix on the 2.17 branch.
I will take care of your contribution.
Thanks a lot.
> Camel Netty4 allowSerializedHeaders
> -----------------------------------
>
> Key: CAMEL-10343
> URL: https://issues.apache.org/jira/browse/CAMEL-10343
> Project: Camel
> Issue Type: Improvement
> Components: camel-netty4
> Affects Versions: 2.17.2
> Reporter: Nicolas Duffillot
> Assignee: Andrea Cosentino
> Labels: patch
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> When transferExchange = true, NettyPayloadHelper.getIn(NettyEndpoint,
> Exchange) calls DefaultExchangeHolder.marshal(exchange) that calls
> DefaultExchangeHolder.marshal(exchange, true, false);
> Third parameter "allowSerializedHeaders" is forced to false and there seems
> to be no way to call the marshal method with this parameter set to true.
> Because of that, the marshalling of the exchange properties doesn't include
> the serializable pojos as the "DefaultExchangeHolder.getValidHeaderValue"
> method excludes those serailizable object when allowSerializedHeaders=false :
> if (allowSerializedHeaders) {
> if (headerValue instanceof Serializable) {
> return headerValue;
> }
> }
> Hoping to be clear enough.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
