Jackson XML

When using Data Format in Spring DSL, you need to declare the data formats first. This is done in the dataFormats XML tag:

And then you can refer to this id in the route:

When marshalling a POJO to XML, you might want to exclude certain fields from the XML output. With Jackson, you can use JSON views to accomplish this. First, create one or more marker classes.

Use the marker classes with the @JsonView annotation to include/exclude certain fields. The annotation also works on getters.

Finally, use the Camel JacksonXMLDataFormat to marshall the above POJO to XML.

Note that the weight field is missing in the resulting XML:

As an example of using this attribute, you can instead of:

Directly specify your JSON view inside the Java DSL as:

And the same in XML DSL:

If you want to marshal a POJO to XML, and the POJO has some fields with null values. And you want to skip these null values, then you need to set either an annotation on the POJO:

But this requires you to include that annotation in your POJO source code. You can also configure the Camel JacksonXMLDataFormat to set the include option, as shown below:

Or from XML DSL you configure this as

If you use Jackson to unmarshal XML to POJO, then you can now specify a header in the message that indicates which class name to unmarshal to. The header has key CamelJacksonUnmarshalType if that header is present in the message, then Jackson will use that as FQN for the POJO class to unmarshal the XML payload as.

For JMS end users, there is the JMSType header from the JMS spec that indicates that also. To enable support for JMSType you would need to turn that on, on the Jackson data format as shown:

Or from XML DSL you configure this as:

If you are using Jackson to unmarshal XML to a list of map/POJO, you can now specify this by setting useList="true" or use the org.apache.camel.component.jacksonxml.ListJacksonXMLDataFormat. For example, with Java, you can do as shown below:

And if you use XML DSL then you configure to use a list using useList attribute as shown below:

And you can specify the POJO type also

You can use custom Jackson modules by specifying the class names of those using the moduleClassNames option as shown below.

When using moduleClassNames then the custom Jackson modules are not configured, by created using default constructor and used as-is. If a custom module needs any custom configuration, then an instance of the module can be created and configured, and then use modulesRefs to refer to the module as shown below:

Multiple modules can be specified separated by comma, such as moduleRefs="myJacksonModule,myOtherModule".

Jackson XML has a number of features you can enable or disable, which its XmlMapper uses. For example, to disable failing on unknown properties when marshalling, you can configure this using the disableFeatures:

You can disable multiple features by separating the values using comma. The values for the features must be the name of the enums from Jackson from the following enum classes:

To enable a feature, use the enableFeatures options instead.

From Java code, you can use the type safe methods from camel-jackson module:

Jackson XmlMapper can be used to convert maps to POJO objects. Jackson component comes with the data converter that can be used to convert java.util.Map instance to non-String, non-primitive and non-Number objects.

If there is a single XmlMapper instance available in the Camel registry, it will be used by the converter to perform the conversion. Otherwise, the default mapper will be used.

Using the prettyPrint option one can output a well-formatted XML while marshalling:

And in Java DSL:

Please note that there are 5 different overloaded jacksonXml() DSL methods which support the prettyPrint option in combination with other settings for unmarshalType, jsonView etc.