Skip to content

CAMEL-10666: exposed uri param to enable inclusion of serializable headers#1370

Closed
davidecavestro wants to merge 1 commit intoapache:camel-2.17.xfrom
davidecavestro:CAMEL-10666
Closed

CAMEL-10666: exposed uri param to enable inclusion of serializable headers#1370
davidecavestro wants to merge 1 commit intoapache:camel-2.17.xfrom
davidecavestro:CAMEL-10666

Conversation

@davidecavestro
Copy link
Contributor

As per CAMEL-10666 this is an enhancement proposal to restore the possibility of saving Serializable headers within the exchange, simply setting to true the new parameter allowSerializedHeaders.

if (endpoint != null && endpoint.isTransferExchange()) {
LOG.trace("Option transferExchange=true so we use JmsMessageType: Object");
Serializable holder = DefaultExchangeHolder.marshal(exchange);
Serializable holder = DefaultExchangeHolder.marshal(exchange, false, endpoint.isAllowSerializedHeaders());
Copy link
Contributor Author

@davidecavestro davidecavestro Jan 3, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The hard coded false argument is there to avoid serializing exchange props, as it seems they may contain some instances of non serializable classes, i.e. for exchange history tracking purposes.
BTW if needed it could be easily exposed an additional parameter to control even this behavior.

@oscerd
Copy link
Contributor

oscerd commented Jan 9, 2017

@davidecavestro can you please open this PR against master? We don't add new option on minor release.

Thanks.

@davidecavestro
Copy link
Contributor Author

@oscerd I've cherry picked the commit and opened a new PR #1386 against master.

zregvart pushed a commit to zregvart/camel that referenced this pull request Jul 9, 2021
[ENTESB-13186] CAMEL-14792: Ensure CAMEL-13468 works without sacrific…
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants