Skip to content

Conversation

@sam0r040
Copy link
Collaborator

@sam0r040 sam0r040 commented Jan 16, 2023

This intended as an attempt to fix issue #116 in a generic way. It adds the possibility to document of the message binding.

Docs:

It is currently only implemented for the springwolf-kafka-plugin.

The API for producing messages has been extended to be able to pick up binding information. The controller in of the kafka plugin will use the key from the binding information when producing the message.

This PR works together with springwolf/springwolf-ui#35

…nge MessageHelper to not expose the TreeSet that is used for deduplication because a TreeSet breaks equals
…ity without relying on equals based on message name
…ion as part of KafkaAsyncOperationBinding to support documentation of kafka keys as message binding
…n empty message binding so that there is always a message binding
…ct class and method level listener scanners to include an empty message binding so that there is always a message binding
…t class and method level listener scanners to include an empty message binding so that there is always a message binding
…cture of KafkaAsyncMessageBinding to contain a new sub-annotation KafkaAsyncKey to make it more obvious what is part of the key documentation and which is part of the kafka message binding, Add default values for message binding to KafkaConsumer- and KafkaProducerData
…ntain an example for the key and to the change that a kafka message binding is always present
…-amqp-pluging to support message bindings which are sent by springwolf-ui
@sam0r040 sam0r040 force-pushed the feature/add_support_for_message_binding branch from 538be62 to e6954fe Compare February 6, 2023 17:17
@timonback timonback merged commit 0efbde7 into springwolf:master Feb 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants