Since Camel 2.12
The Zip Deflater Data Format is a message compression and de-compression format. Messages marshalled using Zip compression can be unmarshalled using Zip decompression just prior to being consumed at the endpoint. The compression capability is quite useful when you deal with large XML and Text based payloads. It facilitates more optimal use of network bandwidth while incurring a small cost in order to compress and decompress payloads at the endpoint.
This dataformat is not for working with zip files such as uncompressing and building zip files. Instead use the zipfile dataformat.
In this example we marshal a regular text/XML payload to a compressed payload employing zip compression
Deflater.BEST_COMPRESSION and send it an ActiveMQ queue called MY_QUEUE.
Alternatively if you would like to use the default setting you could send it as
In this example we unmarshal a zipped payload from an ActiveMQ queue called MY_QUEUE to its original format, and forward it for processing to the UnZippedMessageProcessor. Note that the compression Level employed during the marshalling should be identical to the one employed during unmarshalling to avoid errors.
Spring Boot Auto-Configuration
When using zipDeflater with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
<dependency> <groupId>org.apache.camel.springboot</groupId> <artifactId>camel-zip-deflater-starter</artifactId> <version>x.x.x</version> <!-- use the same version as your Camel core version --> </dependency>
The component supports 3 options, which are listed below.
Whether to enable auto configuration of the gzipDeflater data format. This is enabled by default.
To specify a specific compression between 0-9. -1 is default compression, 0 is no compression, and 9 is the best compression.
Whether to enable auto configuration of the zipDeflater data format. This is enabled by default.