Solace Operation Binding v0.3.0

The Solace operation binding v0.3.0 specifies the array of destinations that a message will be sent to or received from.

Overview

This binding allows you to define a list of destinations for a single operation, where each destination can be a queue or a direct topic subscription.

Operation Properties

Property	Type	Required	Description
bindingVersion	string	No	Binding version (defaults to 0.3.0).
destinations	array	No	An array of destination objects.

---

Destination Object

Each object in the destinations array defines a single destination.

Property	Type	Required	Description
destinationType	string	Yes	queue or topic.
deliveryMode	string	No	direct or persistent. Defaults to direct.
queue	object	No	A queue object, required if destinationType is queue.
topicSubscriptions	array	No	A list of topic subscriptions for a topic destination.

---

Queue Object

The queue object is used when destinationType is queue.

Property	Type	Required	Description
name	string	No	The name of the queue.
topicSubscriptions	array	No	A list of topic subscriptions that the queue listens to.
accessType	string	No	exclusive or nonexclusive.
maxMsgSpoolUsage	string	No	Maximum spool usage for the queue (e.g., "100MB").
maxTtl	string	No	Maximum time-to-live for messages spooled to the queue (e.g., "3600s").

---

Example

This operation describes a consumer that binds to a durable queue for guaranteed delivery.

operations:
  receiveOrderEvent:
    action: receive
    bindings:
      solace:
        bindingVersion: '0.3.0'
        destinations:
          - destinationType: 'queue'
            deliveryMode: 'persistent'
            queue:
              name: 'q_orders'
              topicSubscriptions:
                - 'orders/v1/us/new'

Changelog

Version 0.3.0

• Introduced the destinations array to formally define multiple endpoints for an operation.