Skip to content

Fix CloudEvents unwrap for inline listeners - #2308

Merged
jeremydmiller merged 1 commit into
JasperFx:mainfrom
lahma:kafka-multiple-cloud-events
Mar 16, 2026
Merged

jeremydmiller merged 1 commit into
JasperFx:mainfrom
lahma:kafka-multiple-cloud-events

Conversation

@lahma

@lahma lahma commented Mar 16, 2026

Copy link
Copy Markdown
Contributor

This was actually the fast path to get to #2306 problems. So when there was no default message type to fallback to and Kafka envelope didn't have eventType the routing wasn't able to extract it from cloud event envelope.

Now allowing the handler pipeline to unwrap metadata-aware serializers before requiring Envelope.MessageType so inline CloudEvents receivers can deserialize messages without DefaultIncomingMessage(). Reuse the same helper in durable receivers and add runtime and Kafka regression coverage for inline CloudEvents handling.

Allow the handler pipeline to unwrap metadata-aware serializers before
requiring Envelope.MessageType so inline CloudEvents receivers can
deserialize messages without DefaultIncomingMessage<T>(). Reuse the same
helper in durable receivers and add runtime and Kafka regression
coverage for inline CloudEvents handling.
@lahma
lahma force-pushed the kafka-multiple-cloud-events branch from 97dc81a to 5866083 Compare March 16, 2026 19:04
@jeremydmiller
jeremydmiller merged commit c2d996f into JasperFx:main Mar 16, 2026
5 of 10 checks passed
@lahma
lahma deleted the kafka-multiple-cloud-events branch March 16, 2026 19:31
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.

2 participants