[[unmarshal-eip]]
= Unmarshal EIP

If you receive a message from one of the Camel xref:ROOT:index.adoc[Components] such as xref:ROOT:file-component.adoc[File], xref:ROOT:http-component.adoc[HTTP] or xref:ROOT:jms-component.adoc[JMS] you often want to unmarshal the payload into some bean so that you can process it using some xref:manual:ROOT:bean-integration.adoc[Bean Integration] or perform xref:manual:ROOT:predicate.adoc[Predicate] evaluation and so forth.


== Options

// eip options: START
The Unmarshal EIP supports 1 options which are listed below:

[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
| *dataFormatType* | *Required* The data format to be used |  | DataFormatDefinition
|===
// eip options: END

== Samples

For example

[source,java]
----
DataFormat jaxb = new JaxbDataFormat("com.acme.model");

from("activemq:My.Queue").
  unmarshal(jaxb).
  to("mqseries:Another.Queue");
----

The above uses a named DataFormat of _jaxb_ which is configured with a number of Java package names. You can if you prefer use a named reference to a data format which can then be defined in your xref:manual:ROOT:registry.adoc[Registry] such as via your xref:ROOT:spring-summary.adoc[Spring] XML file.

You can also use the DSL itself to define the data format as you use it.
For example the following uses Java serialization to unmarshal a binary
file then send it as an ObjectMessage to xref:ROOT:activemq-component.adoc[ActiveMQ]

[source,java]
----
from("file://foo/bar").
  unmarshal().serialization().
  to("activemq:Some.Queue");
----

