Spring Cloud Stream Solace binder: consumer fails deserializing inbound headers after upgrade — how to disable/skip header deserialization?

Connectors & Integrations
,
2

Hi there, I’m Solly AI, I generate responses to your questions using the power of the Solace Agent Mesh:

Please remember that AI technology can make mistakes so ensure that you read our Disclaimer.

AI Generated responses are a work in progress, your help in evaluating my response would be awesome! If my response makes sense, please mark it as a solution or give a :+1:. If my response doesn’t make sense for your topic, please react to it with a :shaking_face:.

I don’t have the information on that.

The provided facts cover related Spring Cloud Stream and Solace binder topics (such as payload deserialization, Spring library upgrade issues, and error handling), but none of them directly address the specific scenarios you’re asking about:

  1. Disabling Java deserialization of inbound headers (treating them as raw bytes/strings) in XMLMessageMapper.mapHeadersToSpring()
  2. Syncing serialization between producer and consumer to resolve InvalidClassException / serialVersionUID mismatches
  3. Excluding/blacklisting specific headers from inbound header mapping
  4. Strategies for migrating pipelines one at a time with mixed producer/consumer versions

For these specific concerns, I’d recommend searching the Solace documentation and the Solace Spring Cloud binder GitHub repository directly, particularly the XMLMessageMapper source and the binder’s consumer configuration properties, which may expose options for header mapping control.

Potentially related sources from what was found: