You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello.
My idea is to save raw byte[] message in items before deserialization, I need it further for my logic. But when I save it to MessageContext.Items it disappears after DeserializerMiddleware handles the message.
As far as I understood from the source code, DeserializerConsumerMiddleware invokes SetMessage method that flushes Items collection.
In my opinion it is quite a confusing behavior. As a user I expect that during message handling process message context should be the same along all middlewares, since the message is the same, deserialized or not.
Could you please give some clarification on this subject, whether it is a bug, or a by-design behavior?
Thanks.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello.
My idea is to save raw byte[] message in items before deserialization, I need it further for my logic. But when I save it to MessageContext.Items it disappears after DeserializerMiddleware handles the message.
As far as I understood from the source code, DeserializerConsumerMiddleware invokes SetMessage method that flushes Items collection.
In my opinion it is quite a confusing behavior. As a user I expect that during message handling process message context should be the same along all middlewares, since the message is the same, deserialized or not.
Could you please give some clarification on this subject, whether it is a bug, or a by-design behavior?
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions