camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrea Cosentino (JIRA)" <>
Subject [jira] [Issue Comment Deleted] (CAMEL-10343) Camel Netty4 allowSerializedHeaders
Date Wed, 28 Sep 2016 06:26:21 GMT


Andrea Cosentino updated CAMEL-10343:
    Comment: was deleted

(was: 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:
>             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

View raw message