camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CAMEL-10343) Camel Netty4 allowSerializedHeaders
Date Wed, 28 Sep 2016 07:29:20 GMT

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

Claus Ibsen updated CAMEL-10343:
--------------------------------
    Priority: Minor  (was: Major)

> 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
>            Priority: Minor
>              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)

Mime
View raw message