Chapter 138. Hessian DataFormat (deprecated)
Available as of Camel version 2.17
Hessian is Data Format for marshalling and unmarshalling messages using Caucho’s Hessian format.
If you want to use Hessian Data Format from Maven, add the following dependency to your pom.xml:
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-hessian</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel core version -->
</dependency>138.1. Options
The Hessian dataformat supports 4 options which are listed below.
| Name | Default | Java Type | Description |
|---|---|---|---|
| whitelistEnabled |
|
| Define if Whitelist feature is enabled or not |
| allowedUnmarshallObjects |
| Define the allowed objects to be unmarshalled | |
| deniedUnmarshallObjects |
| Define the denied objects to be unmarshalled | |
| contentTypeHeader |
|
| Whether the data format should set the Content-Type header with the type from the data format if the data format is capable of doing so. For example application/xml for data formats marshalling to XML, or application/json for data formats marshalling to JSon etc. |
138.2. Using the Hessian data format in Java DSL
from("direct:in")
.marshal().hessian();138.3. Using the Hessian data format in Spring DSL
<camelContext id="camel" xmlns="http://camel.apache.org/schema/spring">
<route>
<from uri="direct:in"/>
<marshal ref="hessian"/>
</route>
</camelContext>
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.