XML JSON Data Format (camel-xmljson)

Available as of Camel 2.10

Camel already supports a number of data formats to perform XML and JSON-related conversions, but all of them require a POJO either as an input (for marshalling) or produce a POJO as output (for un-marshaling). This data format provides the capability to convert from XML to JSON and viceversa directly, without stepping through intermediate POJOs.

This data format leverages the Json-lib library to achieve direct conversion. In this context, XML is considered the high-level format, while JSON is the low-level format. Hence, the marshal/unmarshal semantics are assigned as follows:

  • marshalling => converting from XML to JSON
  • un-marshaling => converting from JSON to XML.


This data format supports the following options. You can set them via all DSLs. The defaults marked with (*) are determined by json-lib, rather than the code of the data format itself. They are reproduced here for convenience to avoid having to consult the json-lib documentation directly.







UTF-8 (*)

Used when un-marshaling (JSON to XML conversion).

Sets the encoding for the call to XMLSerializer.write() method, hence it is only used when producing XML.
However, when producing JSON, the encoding is determined by the input String being processed.

If the conversion is performed on an InputStreamjson-lib uses the platform's default encoding, e.g., determined by the file.encoding system property.



'e' (*)

Used when un-marshaling (JSON to XML conversion).

Specifies the name of the XML elements representing each array element.

See json-lib doc.



'a' (*)

Used when un-marshaling (JSON to XML conversion).

Specifies the name of the top-level XML element.

For example, when converting:

[1, 2, 3]

it is, by default, translated as:


By setting this option or rootName, you can alter the name of the element a.



none (*)

Used when un-marshaling (JSON to XML conversion).

When converting any JSON construct (object, array, null) to XML (un-marshaling), this option specifies the name of the top-level XML element.

If not set, json-lib will use arrayName or objectName (default value: o, at the current time it is not configurable in this data format).

If set to root, the JSON string:

{ "x": "value1", "y" : "value2" } 

is translated as:


otherwise the root element would be named o.



false (*)

Used when un-marshaling (JSON to XML conversion).

According to the json-lib docs: "Flag to be tolerant to incomplete namespace prefixes."

In most cases, json-lib automatically changes this flag at runtime to match the processing.




Used when un-marshaling (JSON to XML conversion).

Binds namespace prefixes and URIs to specific JSON elements. 

NamespacesPerElementMapping is a wrapper around an element name + a map of prefixes against URIs.




Used when un-marshaling (JSON to XML conversion).

With expandable properties, JSON array elements are converted to XML as a sequence of repetitive XML elements with the local name equal to the JSON key.

For example, the following JSON: 

{ "number": 1,2,3 }

is normally translated as:


where e can be modified by setting elementName.

However, if number is set as an expandable property, it's translated as:





Used when un-marshaling (JSON to XML conversion).

Adds type hints to the resulting XML to aid conversion back to JSON. See documentation here for an explanation.

TypeHintsEnum comprises the following values, which lead to different combinations of the underlying XMLSerializer's typeHintsEnabled and typeHintsCompatibility flags:

  • TypeHintsEnum.NO => typeHintsEnabled = false

  • TypeHintsEnum.YES =>  typeHintsEnabled = true,  typeHintsCompatibilitytrue

  • TypeHintsEnum.WITH_PREFIX =>  typeHintsEnabled = true,  typeHintsCompatibility = false



false (*)

Used when marshaling (XML to JSON conversion).

Determines whether the resulting JSON will start off with a top-most element whose name matches the XML root element.

If this option is false, the XML string:


is translated as:

{"x": "1", "y": "2"}

If true, it's translated as:

{ "a":  { "x": "1", "y": "2" }}



false (*)

Used when marshaling (XML to JSON conversion).

Determines whether white spaces between XML elements will be regarded as text values or disregarded.



false (*)

Used when marshaling (XML to JSON conversion).

Determines whether leading and trailing white spaces will be omitted from String values.



false (*)

Used when marshaling (XML to JSON conversion).

Signals whether namespaces should be ignored. By default they will be added to the JSON output using @xmlns elements.



false (*)

Used when marshaling (XML to JSON conversion).

Removes the namespace prefixes from XML qualified elements, so that the resulting JSON string does not contain them.

Basic Usage With the Java DSL

Explicitly Instantiating the DataFormat

Just instantiate the XmlJsonDataFormat from package org.apache.camel.dataformat.xmljson. Make sure you have installed the camel-xmljson feature (if running on OSGi) or that you've included camel-xmljson-{version}.jar and its transitive dependencies in your classpath.

Example, initialization with a default configuration:

To tune the behavior of the data format as per the options above, use the appropriate setters:

Once the DataFormat is instantiated, the next step is to use it as a parameter to either of the marshal()/unmarshal() DSL elements:

Defining the DataFormat in-line

Alternatively, you can define the data format inline by using the xmljson() DSL element.

If you wish, you can even pass in a Map<String, String> to the inline methods to provide custom options:

Basic Usage with Spring or Blueprint DSL

Within the <dataFormats> block, simply configure an xmljson element with unique IDs:

Then you simply refer to the data format object within your <marshal/> and <unmarshal/> DSLs:

Enabling XML DSL autocompletion for this component is easy: just refer to the appropriate Schema locations, depending on whether you're using Spring or Blueprint DSL. Remember that this data format is available from Camel 2.10. Therefore only schemas from that version or later will include these new XML elements and attributes.

The syntax with Blueprint is identical to that of the Spring DSL. Just ensure the correct namespaces and schemaLocations are in use.

Namespace Mappings

XML has namespaces to fully qualify elements and attributes; JSON doesn't. You need to take this into account when performing XML-JSON conversions.

To bridge the gap, Json-lib has an option to bind namespace declarations in the form of prefixes and namespace URIs to XML output elements while un-marshaling, e.g., converting from JSON to XML.

For example, provided the following JSON string:

you can ask json-lib to output namespace declarations on elements pref1:a and pref2:b to bind the prefixes pref1 and pref2 to specific namespace URIs.

To use this feature, simply create XmlJsonDataFormat.NamespacesPerElementMapping objects and add them to the namespaceMappings option (which is a List).

The XmlJsonDataFormat.NamespacesPerElementMapping holds an element name and a Map of [prefix => namespace URI]. To facilitate mapping multiple prefixes and namespace URIs, the NamespacesPerElementMapping(String element, String pipeSeparatedMappings) constructor takes a String-based pipe-separated sequence of [prefix, namespaceURI] pairs in the following way: |ns2|http://camel.apache.org/personalData|ns3|http://camel.apache.org/personalData2|.

In order to define a default namespace, just leave the corresponding key field empty: |ns1|http://camel.apache.org/test1||http://camel.apache.org/default|.

Binding namespace declarations to an element name = empty string will attach those namespaces to the root element.

The code for this is:

And you can achieve the same in Spring DSL.


Using the namespace bindings in the Java snippet above on the following JSON string:


Would yield the following XML:

Remember that the JSON spec defines a JSON object as follows:

An object is an unordered set of name/value pairs. [...].

That's why the elements are in a different order in the output XML.


To use the XmlJson dataformat in your camel routes you need to add the following dependency to your pom.

See Also

© 2004-2015 The Apache Software Foundation.
Apache Camel, Camel, Apache, the Apache feather logo, and the Apache Camel project logo are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners.
Graphic Design By Hiram