Versions Compared

Old Version 4

changes.mady.by.user Keith Babo

Saved on

compared with

New Version 5

changes.mady.by.user willem jiang

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The dozer: component provides the ability to map between Java beans using the Dozer mapping framework since Camel 2.15.0.  Camel also supports the ability to trigger Dozer mappings as a type converter.  The primary differences between using a Dozer endpoint and a Dozer converter are:

...

Name

Default

Description

mappingFile

dozerBeanMapping.xml

The location of a Dozer configuration file. The file is loaded from the classpath by default, but you can use file:, classpath:, or http: to load the configuration from a specific location.

unmarshalId

none

The id of a dataFormat defined within the Camel Context to use for unmarshalling the mapping input from a non-Java type.

 

marshalId

none

The id of a dataFormat defined within the Camel Context to use for marshalling the mapping output to a non-Java type.

sourceModel

none

Fully-qualified class name for the source type used in the mapping. If specified, the input to the mapping is converted to the specified type before being mapped with Dozer.

targetModel

none

Fully-qualified class name for the target type used in the mapping. This option is required.

mappingConfiguration

none

The name of a DozerBeanMapperConfiguration bean in the Camel registry which should be used for configuring the Dozer mapping. This is an alternative to the mappingFile option that can be used for fine-grained control over how Dozer is configured. Remember to use a "#" prefix in the value to indicate that the bean is in the Camel registry (e.g. "#myDozerConfig").

...