All Classes and Interfaces
Class
Description
This service is responsible for scheduling a job that will submit messages
to the subscription processing pipeline at a given interval.
The purpose of this service is to submit messages to the processing pipeline for which previous attempts at
submission has failed.
This is used by "message" type subscriptions to provide a key to the message wrapper before submitting it to the channel
This service provides two distinct contexts in which it submits messages to the subscription pipeline.
Definition of a REST Hook channel validator that perform checks on the channel payload and endpoint URL.
A concrete instantiation of this interface should provide tailored validation of an endpoint URL
throwing
RuntimeException upon validation failure.Responsible for transitioning subscription resources from REQUESTED to ACTIVE
Once activated, the subscription is added to the SubscriptionRegistry.
This interceptor can be used for troubleshooting subscription processing.
This interceptor is responsible for submitting operations on resources to the subscription pipeline.
This Spring config should be imported by a system that pulls messages off of the
matching queue for processing, and handles delivery
Responsible for transitioning subscription resources from REQUESTED to ACTIVE
Once activated, the subscription is added to the SubscriptionRegistry.
Cache of active subscriptions.
This Spring config should be imported by a system that submits resources to the
matching queue for processing
Subscription topic notifications are natively supported in R5, R4B.
Responsible for transitioning subscription resources from REQUESTED to ACTIVE
Once activated, the subscription is added to the SubscriptionRegistry.
Utilities for working with the subscription resource
The purpose of this interceptor is to synchronously submit ResourceModifiedMessage to the
subscription processing pipeline, ie, as part of processing the operation on a resource.