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
{{ message }}
This repository has been archived by the owner on Jul 2, 2023. It is now read-only.
I was trying to move my consumer configuration outside of the code and into the application.yml file, but i stumbled with an issue in configuration validation.
According to the documentation, the following configuration should be valid for a queue consumer:
VehicleConsumer:
queue: 'vehiclesQueue-it'
But the ConsumerConfigurationImpl class does this check when validating the configuration.
However, the binding and match properties shouldn't be required when binding a consumer to a queue. Adding them to my yml configuration with bogus values makes the validation pass, but IMHO the check should be fixed.
Note: i did some debugging and noted that when loading configuration from a yml file the binding property is populated with an empty Map instead of being null, so the check fails. Thus, to make the validation pass it's sufficient to add the match property to the consumer configurations, but it shouldn't be needed anyway.
The text was updated successfully, but these errors were encountered:
I was trying to move my consumer configuration outside of the code and into the application.yml file, but i stumbled with an issue in configuration validation.
According to the documentation, the following configuration should be valid for a queue consumer:
But the
ConsumerConfigurationImpl
class does this check when validating the configuration.However, the
binding
andmatch
properties shouldn't be required when binding a consumer to a queue. Adding them to my yml configuration with bogus values makes the validation pass, but IMHO the check should be fixed.Note: i did some debugging and noted that when loading configuration from a yml file the
binding
property is populated with an empty Map instead of being null, so the check fails. Thus, to make the validation pass it's sufficient to add thematch
property to the consumer configurations, but it shouldn't be needed anyway.The text was updated successfully, but these errors were encountered: