Spring-xd redis message bus removing headers from the message -

I'm using redis as my message archive for spring-xd distributed env.

I send message header as below,

  oufinalTreeMapsg1 = messbilder. With payload (tree map) .setHeader ("columnNames", columnNames) .build ();  

It only shows ID and timestamp while checking the message received in the processor

The header during sending

  [headers = {ColumnNames = ABC, DEF, ID = 74acf995-ec39-0e1c-a426-c9e27b1d47d6, timestamp = 1406784568493}]  

received header

  [header = {Id ad 8dc5b-5b24-d444-7583-c2da7a21d31c, timestamp = 1406784568495}]  

Here id and timestamps are different but payloads are similar.

Please help me to resolve this issue,

Thank you in advance, -Success

The radis message does not support passing custom headers by default; However, you can add custom headers to those customers by adding a comma-delimited list to the third party, which is redis-bus.xml in & lt; Constructor-arg / & gt; Xd-In Dirt Jar) For example ...

... will pass the header foo and times .

However, only simple string values ​​can be passed.

In spring integration (used by bus), the messages are irreversible; When they are taken to some mediums (like the Radis message bus), a new message is created with the content, but those headers (IDs and timestamps) will change.

RabbitMessageBus by default all custom headers.

UPDATE

There is no concept of message headers or properties near radis and cuffs.

Cuff Message Bus Implementation now supports properties in servers.yml, which is to add custom headers to those people who are taken to the bus.

By default, only some system level headers are moved.

View Header: In servers.yml In.

Comma-delimited list of additional (string-valuable) header names for transport

Note that this (for redis) incorrectly says Is that it should be string-value. This was originally the case, but now any object can be converted from / to JSN / in the header value.

In addition, Kafa has a raw mode, in which case a header is expressed on the bus at the bus; It may be desired for performance reasons, but things (such as message type conversion) can not be supported in this mode because the framework can not determine the type.