Skip to content

GH-1776 - Resolve Rabbit Jackson configuration conflict - #1788

Open
DragonFSKY wants to merge 1 commit into
spring-projects:mainfrom
DragonFSKY:gh-1776-rabbit-jackson-conflict
Open

GH-1776 - Resolve Rabbit Jackson configuration conflict#1788
DragonFSKY wants to merge 1 commit into
spring-projects:mainfrom
DragonFSKY:gh-1776-rabbit-jackson-conflict

Conversation

@DragonFSKY

Copy link
Copy Markdown

Fixes #1776.

When Jackson 2 and Jackson 3 mappers are both available, both Rabbit auto-configurations attempt to register the same rabbitTemplateCustomizer bean.

This orders the Jackson 3 configuration before the deprecated Jackson 2 fallback and makes both default customizers back off by bean name. Differently named customizers can still coexist.

Tests

  • RabbitJacksonConfigurationIntegrationTests: 4 tests passed
  • ./mvnw -pl spring-modulith-events/spring-modulith-events-amqp verify: 21 tests passed

A broader -am verify run was blocked before reaching the AMQP module by unrelated JDBC V2 schema failures.

Order the Jackson 3 configuration before the deprecated Jackson 2 fallback and make both default customizers back off by bean name.

Add coverage for Jackson selection, fallback, and user-defined customizers.

Signed-off-by: dragonfsky <dragonfsky@gmail.com>
@DragonFSKY
DragonFSKY force-pushed the gh-1776-rabbit-jackson-conflict branch from 3e5c84a to 3a193d3 Compare August 6, 2026 13:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

RabbitJackson2Configuration and RabbitJacksonConfiguration conflict when Jackson 2.x is on classpath (e.g. Eureka Client)

1 participant