Skip to content

Conversation

@Crustack
Copy link

Closes #3220

I looked at how e.g. MQTT messages are converted via e.g. StringMessageConverter and came up with the following changes:

  • Removed the String/generic JSON deserialization from IncomingRabbitMQMessage.convertPayload
  • Added MessageConverter implementations for deserialization to String, JsonObject, JsonArray to comply with current behaviour
  • Added MessageConverter implemenation for deserialization to any type if a JsonMapping implementation is on the classpath
  • Added fromJson(String str, Type type) to JsonMapping interface with implementations for jackson + jsonb (Vert.x does not seem to support mapping for a java.lang.reflect.Type ?)

@Crustack Crustack force-pushed the feat/rabbitmq-message-converters branch from 4a660c7 to 92e8c3b Compare November 29, 2025 11:33
@Crustack
Copy link
Author

Crustack commented Dec 17, 2025

@cescoffier @ozangunalp any chance of getting a first review for this before christmas?
No pressure, I would just prefer this to not get lost between the years 🙂

@ozangunalp
Copy link
Collaborator

I don't think this will be merged before next year. But this, message converters and overall a common connector agnostic Serde is on my short list. So do not worry. We'll advance on it very shortly!

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.

RabbitMQ- Allow Deserialization to complex objects

2 participants