[[DozerTypeConversion-DozerTypeConversion]]
= Dozer Type Conversion

https://github.com/DozerMapper/dozer/blob/master/docs/asciidoc/about/about.adoc[Dozer] is a fast
and flexible framework for mapping back and forth between Java Beans.
Coupled with Camel's automatic type conversion, it's a formidable tool
for dealing object to object mapping headaches that crop up in
enterprise integration projects.

To explain how Dozer can be used within Camel we'll use the following
example of a simple Customer Support Service. The initial version of the
Service defined a 'Customer' object used with a very flat structure.

*Legacy Customer Service Class*

[source,java]
-----------------------------------------------------------------------------------
public class Customer {
    private String firstName;
    private String lastName;
    private String street;
    private String zip;

    public Customer() {}

    public Customer(String firstName, String lastName, String zip, String street) {
        this.firstName = firstName;
        this.lastName = lastName;
        this.zip = zip;
        this.street = street;
    }

    public String getFirstName() {
        return firstName;
    }

    public void setFirstName(String firstName) {
        this.firstName = firstName;
    }

    ... getters and setters for each field
-----------------------------------------------------------------------------------

In the next version it was decided to structure the data better in the
model by moving the address data into its own type, with the resulting
domain object ending up looking like the below.

*Next Gen Customer object*

[source,java]
-------------------------------------------------------------------------
public class Customer {
    private String firstName;
    private String lastName;
    private Address address;

    public Customer() {}

    public Customer(String firstName, String lastName, Address address) {
        this.firstName = firstName;
        this.lastName = lastName;
        this.address = address;
    }
    ....


public class Address {
    private String zipCode;
    private String streetName;

    public Address() {}

    public Address(String zipCode, String streetName) {
        this.zipCode = zipCode;
        this.streetName = streetName;
    }
-------------------------------------------------------------------------

Much nicer! But as often occurs, the previous version of the service,
with the old flat 'Customer' object, was in production with a client and
the project must support the legacy interface. To support both versions,
we must add a mechanism to convert between the old Customer service type
and the new Customer domain type and back again. It would be a simple
matter to write a custom converter class to map between them, but this
may not be the only service/domain inconsistency and these tedious and
error prone custom mappings could quickly start to add up, and bugs with
them.

To a large extent the two objects share an identical structure, with only
the address representation being different. It would be very helpful if
there were a practical way to to automate this kind of mapping, such
that the similar properties could get mapped automatically and only the
inconsistencies requiring custom mapping.

This is where Dozer comes in; it uses reflection to map data between two
bean types using a set of simple mapping rules. Where no rule is
specified, Dozer will attempt to map between them by using matching
properties of two beans. In this way, focus can be given to the
inconsistencies between the beans i.e. the address properties, knowing
that Dozer will automatically match and convert the others.

[[DozerTypeConversion-ConfiguringDozer]]
== Configuring Dozer

Dozer's configuration is extremely flexible and many mapping scenarios
are covered https://github.com/DozerMapper/dozer/blob/master/docs/asciidoc/documentation/mappings.adoc[here].
For our simple example, the configuration looks like the following.

*mapping.xml*

[source,xml]
---------------------------------------------------------------------------------------------------------
<mappings xmlns="http://dozermapper.github.io/schema/bean-mapping"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xsi:schemaLocation="http://dozermapper.github.io/schema/bean-mapping http://dozermapper.github.io/schema/bean-mapping.xsd">
  <mapping>
    <class-a>org.apache.camel.converter.dozer.service.Customer</class-a>
    <class-b>org.apache.camel.converter.dozer.model.Customer</class-b>
    <field>
      <a>street</a>
      <b>address.streetName</b>
    </field>
    <field>
      <a>zip</a>
      <b>address.zipCode</b>
    </field>
  </mapping>
</mappings>
---------------------------------------------------------------------------------------------------------

[[DozerTypeConversion-SupportforDozerinCamel]]
== Support for Dozer in Camel

Camel provides a simple mechanism to integrate Dozer Mappers with it's
own powerful http://camel.apache.org/type-converter.html[Type
Conversion] framework. Its configured by creating an instance of
`DozerTypeConverterLoader` providing it the camel context and an
optional Dozer mapper. If no mapper is supplied, Camel's registry will
be searched for suitable instances. The loader will query the Dozer
Mapper for the types it converts and register them with Camel's
type conversion framework to be handled by the mapper.

[NOTE]
====
*Limitation*

The Camel Dozer type converter does not support having the same type
conversion paris in different mapping ids (eg map-id) in Dozer.
====

In Java it can be configured as follows:

[source,java]
-----------------------------------------------------------------------------------------
Mapper mapper = DozerBeanMapperBuilder.create()
                .withMappingFiles("mapping.xml")
                .build();

new DozerTypeConverterLoader(camelContext, mapper);
-----------------------------------------------------------------------------------------

Or in Spring:

[source,xml]
--------------------------------------------------------------------------------------------------
<bean id="dozerConverterLoader" class="org.apache.camel.converter.dozer.DozerTypeConverterLoader">
  <argument index="0" ref="myCamel"/>
  <argument index="1" ref="mapperConfiguration"/>
</bean>

<bean id="mapperConfiguration" class="org.apache.camel.converter.dozer.DozerBeanMapperConfiguration">
  <property name="mappingFiles">
    <list>
      <value>mapping.xml</value>
    </list>
  </property>
</bean>
 
<camelContext id="myCamel" xmlns="http://camel.apache.org/schema/spring">
  ...
</camelContext>
--------------------------------------------------------------------------------------------------

Or in OSGi Blueprints:

[source,xml]
--------------------------------------------------------------------------------------------------
<bean id="dozerConverterLoader" class="org.apache.camel.converter.dozer.DozerTypeConverterLoader">
  <argument index="0" ref="myCamel"/>
  <argument index="1" ref="mapperConfiguration"/>
</bean>

<bean id="mapperConfiguration" class="org.apache.camel.converter.dozer.DozerBeanMapperConfiguration">
  <property name="mappingFiles">
    <list>
      <value>mapping.xml</value>
    </list>
  </property>
</bean>
 
<camelContext id="myCamel" xmlns="http://camel.apache.org/schema/blueprint">
  ...
</camelContext>
--------------------------------------------------------------------------------------------------

You should of noticed that the configuration for Spring or OSGi Blueprints
is the same, except for the 'xmlns' for the 'camelContext'.

Now, where necessary, Camel will use Dozer to do conversions; in our
case between the new domain and legacy Customer types e.g.

[source,java]
---------------------------------------------------------------------------------------------------------------------------------------------
// given the following route
from("direct:legacy-service-in").bean(new CustomerProcessor());

// and a processor

public class CustomerProcessor {

    public Customer processCustomer(org.apache.camel.converter.dozer.model.Customer customer) {
       ...
    }
}

// service objects can be sent to the processor and automagically converted by Camel & Dozer
template.sendBody("direct:legacy-service-in", new org.apache.camel.converter.dozer.service.Customer("Bob", "Roberts", "12345", "1 Main st."));
---------------------------------------------------------------------------------------------------------------------------------------------
