Closed mlkristiansen closed 3 years ago
Thsi relates to version 2.0.0.RC2
When configuring a custom message converter, the class specification only works in a Groovy config file, not yaml.
Example that works (Groovy):
jms { converters { events { clazz = events.support.jms.EventsJmsMessageConverter } } adapters { events { meta { parentBean = "standardJmsListenerAdapter" } messageConverterBean = "eventsJmsMessageConverter" } } }
This doesn't work:
jms: converters: events: clazz: events.support.jms.EventsJmsMessageConverter adapters: events: meta: parentBean: standardJmsListenerAdapter messageConverterBean: eventsJmsMessageConverter
And the documentation states that the message converter clazz has to be under a "meta" which is incorrect. It has to be placed as a child to the custom name.
Stale issue message
Thsi relates to version 2.0.0.RC2
When configuring a custom message converter, the class specification only works in a Groovy config file, not yaml.
Example that works (Groovy):
This doesn't work:
And the documentation states that the message converter clazz has to be under a "meta" which is incorrect. It has to be placed as a child to the custom name.