SatyamPandey-07 commented on issue #9243:
URL: https://github.com/apache/camel-quarkus/issues/9243#issuecomment-5832714916
Thanks for the feedback, @jamesnetherton.
That makes complete sense regarding backward compatibility and parity with
Camel Spring Boot and upstream Camel behavior. Changing
autoDiscoverObjectMapper to true globally by default could indeed impact
existing applications that rely on an isolated ObjectMapper instance for REST
DSL.
To avoid breaking changes while still improving developer experience for
Quarkus users who expect CDI-managed Jackson beans to bind seamlessly, what are
your thoughts on one of the following approaches?
Add an opt-in configuration property (Defaulting to false): Introduce a
configuration property such as:
properties
quarkus.camel.jackson.rest.auto-discover-object-mapper=false # default is
false for backwards compatibility
When set to true, the customizer would automatically apply
autoDiscoverObjectMapper=true without requiring boilerplate in every
RouteBuilder.restConfiguration().
Keep the current behavior and enhance docs/guidance: Retain the existing
manual restConfiguration().dataFormatProperty("autoDiscoverObjectMapper",
"true") requirement and evaluate changing defaults only in a future major
version if upstream Camel aligns.
Happy to adapt the PR
([#9244](https://github.com/apache/camel-quarkus/pull/9244)) to introduce the
configuration property or close it if the preference is to keep the current
explicit mechanism as-is.
--
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]
