Closed Keisuki closed 2 years ago
Hi! Thanks for using Occurrent and thanks for reporting this issue. I'll look into it :)
I've fixed it now! Will make a new release.
Fantastic! That was really quick
I've released version 0.14.5 which should address the issue :) Thanks again for reporting!
Hi guys. This appears to be a bug, but if I'm just using it wrong, feel free to tell me to go away :smile:
When converting a domain event to a
CloudEvent
,JacksonCloudEventConverter
correctly uses itscloudEventTypeMapper
to decide what event type string to include in the event. This allows the user to inject their own type mapper, decoupling the event type string from the fully qualified Java class name.However, when converting back to a domain event from a
CloudEvent
, it appears to ignore thecloudEventTypeMapper
entirely and determine the class to deserialize to based on the type string as a fully qualified Java class nameHere's an example of code which exhibits this bug:
This outputs the following:
Using a debugger, we can see that
getDomainEventType
onMyCloudEventTypeMapper
is never invoked.