Hi everyone,
We’ve just released NServiceBus.Envelope.CloudEvents 1.0.2.
Fixed bugs
- #154 Mapped CloudEvent types fail deserialization when the type is not already registered
How to know if you are affected
You are affected if all of the following apply:
- You use NServiceBus.Envelope.CloudEvents 1.0.0 or 1.0.1.
- The endpoint receives CloudEvents with types configured through
CloudEventsConfiguration.TypeMappings. - The incoming CloudEvent’s mapped .NET type is not registered in the endpoint’s message metadata registry, or its type maps to multiple .NET types.
Mapped types can be unregistered when assembly scanning is disabled or their assemblies are excluded from scanning. This can affect messages with handlers for interfaces or base types.
Symptoms
Messages fail with a MessageDeserializationException and are moved to the error queue. This can happen even when a handler exists for an interface or base type of the mapped concrete type. If no handler exists, this error replaces the expected missing-handler exception.
When to upgrade
You should upgrade immediately if you are affected. Otherwise, you should upgrade during your next maintenance window.
If a suitable handler exists, retry affected messages from the error queue after upgrading and restarting the endpoint. Messages without a handler still require you to add one.
Where to get it
You can install NServiceBus.Envelope.CloudEvents 1.0.2 from NuGet.
Please read our release policy for more details.
With thanks,
The team in Particular