All Classes and Interfaces

Class
Description
 
 
 
 
 
 
 
 
 
 
 
 
Enriched shadow of a hierarchy lookup result, for conveying compliance statuses for each element in an aggregated structure.
 
Hierarchy level statistics for a compliance hierarchy lookup.
 
 
 
 
 
 
 
 
 
Request parameters for compliance hierarchy lookup.
Use this service to get an aggregation hierarchy enriched by respective compliance statuses for each node.
 
 
 
 
 
 
 
 
 
 
 
CREATE TABLE IF NOT EXISTS compliance_log_entry ( `saga_event_id` CHAR(36) CHARACTER SET latin1, `compliance_repository` VARCHAR(255), `log_id` CHAR(36) CHARACTER SET latin1, `request` TEXT, `request_time` DATETIME, `response` TEXT, `response_time` DATETIME, `message_type` VARCHAR(255), PRIMARY KEY(`saga_event_id`, `compliance_repository`, `log_id`), INDEX `request_time_idx` (`request_time`) )
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Deprecated.
 
CREATE TABLE IF NOT EXISTS compliance_reply ( `saga_event_id` CHAR(36) CHARACTER SET latin1, `reply_identifier` VARCHAR(255), `compliance_repository` VARCHAR(255), `epcis_event_id` VARCHAR(255), `status` VARCHAR(255) CHARACTER SET latin1, `status_reason` TEXT, `created_at` DATETIME, `extra_details` TEXT, `message_type` VARCHAR(255), PRIMARY KEY(`saga_event_id`, `compliance_repository`, `reply_identifier`), INDEX `created_at_idx` (`created_at`) )
 
 
 
 
 
 
 
Deprecated.
 
 
 
 
 
 
 
A wrapper used to comply with the method names of IComplianceRepository, originating from ComplianceCassandraRepository.
 
 
 
 
Deprecated.
 
 
 
 
 
 
 
 
This is based on the implementation from Saga Core
 
 
Result of dispatching messages.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Implement this to validate events
 
 
 
 
 
 
 
 
 
 
 
 
Customize the way of how events should be dispatched during ComplianceSubscriptionProcessor processing.
Decide which events should be dispatched in which topics.
 
Implement an acceptor that analyses an event and accepts it if it corresponds with the chosen regulation message type
 
Extension point for globally ignoring certain events
Event global processing options
 
 
Implement this so that the dependency analyser can compute which dependencies must be met before the event can be processed or failed by the compliance subscription
 
 
 
 
 
 
 
 
 
 
Implement this service to dynamically provide the recall reason for use in the module.
 
 
 
Revert support extension point
Revert support options
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Extend this to create a new subscription for processing EPCIS events