Spring/spring-integration
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

INT-3939: Consistency for Redis Queue Gateways

Browse Source 
JIRA: https://jira.spring.io/browse/INT-3939

Previously `RedisQueueInboundGateway` and `RedisQueueOutboundGateway` used different `RedisSerializer`s
for non-String objects.

* Change the default to the `JdkSerializationRedisSerializer` for the consistency in case of client/server scenarios.

The previous behavior with the `StringRedisSerializer` can be reinstated with `serializer` injection.

Doc Polishing.
This commit is contained in:
Artem Bilan
2016-01-27 17:32:22 -05:00
committed by Gary Russell
parent f762f2c3f0
commit d2eba0927d
6 changed files with 22 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
src/reference/asciidoc/redis.adoc
View File

@@ -732,7 +732,8 @@ Mutually exclusive with 'redis-template' attribute.
<8> The `RedisSerializer` bean reference.
Can be an empty string, which means 'no serializer'.
In this case the raw `byte[]` from the inbound Redis message is sent to the `channel` as the `Message` payload.
By default it is a `StringRedisSerializer`.
By default it is a `JdkSerializationRedisSerializer`. (Note that in releases before _version 4.3_, it was a
`StringRedisSerializer` by default; to restore that behavior provide a reference to a `StringRedisSerializer`).
<9> The timeout in milliseconds to wait until the receive message will be get or not.

8
src/reference/asciidoc/whats-new.adoc
View File

@@ -80,12 +80,20 @@ See <<content-type-conversion-outbound>> for more information.
==== Redis Changes
===== List Push/Pop Direction
Previously, the queue channel adapters always used the Redis List in a fixed direction,
pushing to the left end and reading from the right end.
It is now possible to configure the reading and writing direction using `rightPop` and `leftPush` options for the
`RedisQueueMessageDrivenEndpoint` and `RedisQueueOutboundChannelAdapter` respectively.
See <<redis-queue-inbound-channel-adapter>> and <<redis-queue-outbound-channel-adapter>> for more information.
===== Queue Inbound Gateway Default Serializer
The default serializer in the inbound gateway has been changed to a `JdkSerializationRedisSerializer` for compatibility
with the outbound gateway.
See <<redis-queue-inbound-gateway>> for more information.
==== HTTP Changes
Previously, with requests that had a body (such as `POST`) that had no `content-type` header, the body was ignored.