Data Formats and Transformation with JSON, XML, CSV, Jackson, and JAXB
Transform data between formats and understand how Camel supports practical message conversion inside real integration flows.
Inside this chapter
- Why Transformation Is So Common
- Marshalling and Unmarshalling
- Common Data Format Tools
- Transformation Design Matters
Series navigation
Study the chapters in order for the clearest path from Camel basics to advanced route design and production operations. Use the navigation at the bottom of each page to move through the full series.
Why Transformation Is So Common
Integration rarely means only moving data unchanged. One system may emit CSV, another expects JSON, another wants XML, and another needs Java objects. Data transformation is therefore central to Camel usage.
Marshalling and Unmarshalling
from("direct:start")
.unmarshal().json()
.marshal().xml()
.to("mock:result");Unmarshalling converts external data into an internal representation. Marshalling converts it back into an output format for another system.
Common Data Format Tools
- Jackson for JSON
- JAXB for XML binding in suitable contexts
- CSV data formats for flat record exchange
- Custom processors for specialized transformations
Transformation Design Matters
Good transformation design preserves meaning, handles invalid payloads safely, logs useful context, and avoids hidden data-loss assumptions. Advanced teams treat transformation rules as business logic, not only plumbing.