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
Spring Cloud Stream have the concept of user supplied default values. The idea is that users may defined per-binder properties, but also "default" properties that should apply to every binder.
In this example, spring.cloud.stream.bindings.input.content-type would be application.json because it's explicitly defined and any other name (e.g. spring.cloud.stream.bindings.output.content-type) would be text/plain because the user has defined a default fallback.
Their existing code is quite complicated because it attempts to merge values manually, it also needs to call .bind twice. See EnvironmentEntryInitializingTreeMap and BindingServiceProperties for the existing implementation. What they really need is hooks that would allow them to introduce this concept without needing to do so much work themselves.
The text was updated successfully, but these errors were encountered:
Spring Cloud Stream have the concept of user supplied default values. The idea is that users may defined per-binder properties, but also "default" properties that should apply to every binder.
For example, the user might define the following:
In this example,
spring.cloud.stream.bindings.input.content-type
would beapplication.json
because it's explicitly defined and any other name (e.g.spring.cloud.stream.bindings.output.content-type
) would betext/plain
because the user has defined a default fallback.Their existing code is quite complicated because it attempts to merge values manually, it also needs to call
.bind
twice. See EnvironmentEntryInitializingTreeMap and BindingServiceProperties for the existing implementation. What they really need is hooks that would allow them to introduce this concept without needing to do so much work themselves.The text was updated successfully, but these errors were encountered: