Croway opened a new pull request, #30012: URL: https://github.com/apache/camel/pull/30012
JIRA: [CAMEL-26981](https://issues.apache.org/jira/browse/CAMEL-26981) - With Camel Main, `camel.dataformat.<name>.*` configured the data format used by `marshal()`/`unmarshal()`, but the Rest DSL binding created new json/xml data formats and only applied `restConfiguration` data format properties (e.g. `camel.dataformat.jackson.include=NON_NULL` was ignored in REST responses). - `RestBindingAdviceFactory` now copies the options of the configured data format into the binding's data formats, as `DataFormatReifier` does for route data formats (CAMEL-22352); the `json.in.`/`json.out.`/`xml.in.`/`xml.out.` properties are applied afterwards and still win. - `objectMapper`, `xmlMapper`, `allowUnmarshallType` and `allowJmsType` are not copied: the generic data format may have created its mapper when it started, the request and response data formats keep their own, and a header must not choose the request body type. Tests: `JacksonRestBindingMainTest` (camel-jackson, new test-scoped `camel-main` dependency). Upgrade guide: 4.24, "camel-main - the camel.dataformat options apply to the Rest DSL binding"; `rest-dsl-binding.adoc` documents the precedence. _Claude Code on behalf of Federico Mariani_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
