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

INT-4285: TCP: Add Elastic Raw Deserializer

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

Buffer grows as needed.
This commit is contained in:
Gary Russell
2017-06-02 12:39:24 -04:00
committed by Artem Bilan
parent a7ad22adcf
commit c3031a2c7c
3 changed files with 85 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
src/reference/asciidoc/ip.adoc
View File

@@ -264,6 +264,7 @@ The `ByteArrayRawSerializer`^*^, converts a byte array to a stream of bytes and
When using this serializer, message reception will hang until the client closes the socket, or a timeout occurs; a timeout will NOT result in a message.
When this serializer is being used, and the client is a Spring Integration application, the client must use a connection factory that is configured with single-use=true - this causes the adapter to close the socket after sending the message; the serializer will not, itself, close the connection.
This serializer should only be used with connection factories used by channel adapters (not gateways), and the connection factories should be used by either an inbound or outbound adapter, and not both.
Also see `ByteArrayElasticRawDeserializer` below.
NOTE: Before version 4.2.2, when using NIO, this serializer treated a timeout (during read) as an end of file and the
data read so far was emitted as a message.
@@ -294,6 +295,11 @@ instead of its super class `AbstractByteArraySerializer`, and implement `doDeser
The buffer will be returned to the pool automatically.
`AbstractPooledBufferByteArraySerializer` also provides a convenient utility method `copyToSizedArray()`.
__Version 5.0__ added the `ByteArrayElasticRawDeserializer`.
This is similar to the deserializer side of `ByteArrayRawSerializer` above, except it is not necessary to set a `maxMessageSize`.
Internally, it uses a `ByteArrayOutputStream` which allows the buffer to grow as needed.
The client must close the socket in an orderly manner to signal end of message.
The `MapJsonSerializer` uses a Jackson `ObjectMapper` to convert between a `Map` and JSON.
This can be used in conjunction with a `MessageConvertingTcpMessageMapper` and a `MapMessageConverter` to transfer selected headers and the payload in a JSON format.