artembilan/spring-integration — comment on commit 2b4f0b6d754df2c83bea1285b1d4b9378c004c4d
File:  line 0
By olegz:

Artem

I've modified it a little (as you can see form below) and although it might appear as completely different it is based on the content provided by you, so its all good. Let me know if you have any objections otherwise please modify and push and we can close this one.
=======
However be aware of some limitations while using persistent implementations of the Message Store

The Message data (payload and headers) is serialized and deserialized using different mechanisms (depending on the implementation of the Message Store). For example; when dealing with JdbcMessageStore only Serializable data is persisted.
However, special attention must be payed to headers that represent certain types of data. For example if one of the headers contains an instance of the MessageChannel upon deserialization you'll end up with different instance of the channel, which directly affects some of the implicit channels
created by the framework (e.g., REPLY_CHANNEL or ERROR_CHANNEL).
As a workaround we suggest to use channel names instead of channel instances when setting those headers, thus allowing it to be resolved in real time by the ChannelResolver.
Also be careful with configuration like this:
gateway -> queue-channel (backed by persistence Message Store) -> service-activator.
Created on the background Temporary Reply Channel will be lost after reading from queue
by service-activator poller.