Get desktop application:
View/edit binary Protocol Buffers messages
Service providing operations for the Query Messaging component of AxonServer
Opens a Query- and Instruction stream to AxonServer.
Message containing Query related instructions for Axon Server
The actual instruction to send
Registers a Query Handler with AxonServer
Unregisters a Query Handler with AxonServer
Grant permits to AxonServer to send a number of messages to the client
Sends a Response to a Query received via the inbound stream
Indicator that all responses for Query have been sent
Sends a response for a Subscription Query that has been received via the inbound stream
Acknowledgement of previously sent instruction via inbound stream
Instruction identifier. If this identifier is set, this instruction will be acknowledged via inbound stream
Queries or Query related instructions from AxonServer for the connected application
The actual query or instruction
Acknowledgement of previously sent instruction via outbound stream
Represents an incoming Query, for which this component is expected to provide a response
Represents an incoming Subscription Query, for which this component is expected to provide a response and updates
Indicator that receiver is no more interested in updates of this query
Indicator that receiver should send more updates of this query
Instruction identifier. If this identifier is set, this instruction will be acknowledged via outbound stream
Sends a point-to-point or scatter-gather Query
Opens a Subscription Query
Message indicating that query has been completed.
Used in:
A unique identifier for this message
The identifier of the incoming query to complete
Message indicating that consumer is requesting more messages from producer.
Used in:
The identifier of the incoming query to complete
Number of messages requested
Used in: ,
The identifier of the query request.
Message representing an incoming Query
Used as request type in: QueryService.Query
Used as field type in: ,
The message ID of the incoming Query
The name of the Query to execute
The timestamp of the Query creation
A payload accompanying the Query
Meta Data providing contextual information of the Query
An object describing the expectations of the Response Type. Deprecated. no longer used in Axon Framework 5
Any instructions for components Routing or Handling the Query
The unique identifier of the client instance dispatching the query
The Name of the Component dispatching the query
Message that represents the Response to a Query
Used as response type in: QueryService.Query
Used as field type in: ,
The unique identifier of the Response Message
An Error Code identifying the type of error, if any
A detailed description of the error, if any
The Payload of the Response Message
Any Meta Data describing the context of the Response Message
Any instructions for components Routing or Handling the Response Message
The unique identifier of the Query to which this is a response
Message containing details of a Registration of a Query Handler in a component
Used in:
The unique identifier of this Message
The name of the Query the Handler is subscribed to
The type of Result this Handler produces
The name of the Component containing the Query Handler
The unique identifier of the Client Instance containing the Query Handler
A message containing an Update of a Query Subscription Response
Used in:
The unique identifier of this Update
The object representing the Update
Meta Data providing contextual information of the Update
The identifier of the Client instance providing the Update
The Component Name of the Client providing the Update
An Error Code identifying the type of error, if any
A detailed description of the error, if any
Message indicating that all relevant Updates have been sent for a Subscription Query, and that no further Updates are available
Used in:
The identifier of the Client instance providing the Update
The Component Name of the Client providing the Update
Message indicating that an Error occurred and that no Updates will be sent for a Subscription Query
Used in:
The identifier of the Client instance providing the Update
The Component Name of the Client providing the Update
The Code describing the type of Error that occurred
A detailed description of the error, if available
Message that represents a Subscription Query
Used in:
A unique identifier for this subscription
The number of messages the Server may send before needing to await additional permits
The Query describing the desire for information
A description of the type of Object expected as Update Responses. Deprecated: queries don't need to provide expected response types
Message describing possible interactions for a Subscription Query
Used as request type in: QueryService.Subscription
Used as field type in:
The actual request. The Subscription Query is opened using a `subscribe`, which opens the flow of updates. Once successful, the `get_initial_result` retrieves the initial result of the subscription. For the server to send more updates than the initial number of permits, use the `flow_control` request to send more permits.
Start a Subscription Query with the given details.
Ends a previously started Subscription Query with the given details
Requests the initial result of a subscription query to be sent. This should always be done after opening the subscription query itself, to remove concurrency conflicts with Update messages. Note that this request is deprecated. It is recommended to retrieve the initial request using a regular query.
Allows the Server to provide additional Updates to be sent. Only the `number_of_permits` field needs to be set on this message.
Represents a Response Message for a Subscription Query
Used as response type in: QueryService.Subscription
Used as field type in:
The unique identifier for this message
The identifier of the subscription query this is a response for
The actual response. The `initial_result` message is sent as a response to `get_initial_result`. An `update` messages is sent for each update available for the query, even before the Initial Result is supplied. The `complete` or `complete_exceptionally` are sent when the publishing side completed the Subscription Query, either regularly (`complete`) or because an error occurred (`complete_exceptionally`).
Provides an Initial Response
Provides an Update Response
Indicates the Query is complete, and no more Updates will be sent
Indicates the Query failed exceptionally, and no more Updates will be sent