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
Description use-native-decoding=true works as expected when there is no function composition. The skipInputConversion flag in SimpleFunctionRegistry is properly set and payload conversion is not attempted.
However, if function composition is used in combination with use-native-encoding=true, the skipInputConversion flag is always false and payload conversion is attempted.
We need to ensure that if setSkipInputConversion is set on a function then even if this function is composed from multiple functions the settings propagates to all of them
Description
use-native-decoding=true
works as expected when there is no function composition. TheskipInputConversion
flag in SimpleFunctionRegistry is properly set and payload conversion is not attempted.However, if function composition is used in combination with
use-native-encoding=true
, theskipInputConversion
flag is alwaysfalse
and payload conversion is attempted.To Reproduce
Using this sample project which is based on the function-composition-rabbit sample
issue2945
profileJsonMessageConverter
; however, we would expectskipInputConversion=true
and converters to not be called.Expected behavior
I would expect the framework to not attempt payload conversion when
use-native-decoding=true
The text was updated successfully, but these errors were encountered: