Bindings
To indicate the binding (protocol) that's documented, there are multiple options to document them. Add at least one binding so that readers know the protocol in use and functionality like publishing works.
To use the protocol specific bindings, ensure that you have added the corresponding plugin.
Operation binding
Operation bindings describe protocol-specific information for the specific action (publish or subscribe). See operation-binding for details.
Supported protocol specific bindings:
@AmqpAsyncOperationBinding
@KafkaAsyncOperationBinding
@JmsAsyncOperationBinding
@SnsAsyncOperationBinding
@SqsAsyncOperationBinding
@StompAsyncOperationBinding
Generic annotation
For custom protocols or properties, use the generic binding.
You can define anything and there is no validation.
@AsyncGenericOperationBinding(
type = "custom-binding",
fields = {
"internal-field=customValue",
"nested.key=nestedValue"
}
)
See Add-Ons / Generic Annotation Binding for more information
Channel binding
Channel bindings describe protocol-specific information for the channel (topic, queue, etc). See channel-binding for details.
Supported protocol specific bindings:
@KafkaAsyncChannelBinding
@GooglePubSubAsyncChannelBinding