All Classes and Interfaces

Class
Description
 
 
 
 
 
 
Event emitted when a permission request is accepted (Auth token obtained).
 
 
 
 
Event handler for accepted permission requests.
 
 
 
 
 
 
 
 
 
 
 
 
Handles AcceptedEvents for permission requests whose data need is AccountingPointDataNeed.
 
 
 
Data need designed to request accounting point information about a customer from their MDA.
The result for accounting point data needs
 
 
 
 
 
 
 
Validated permission event for accounting-point data needs.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
The main configuration for the AIIDA region connector.
Represents a generic status message for a permission
 
 
Result type for the calculation of AIIDA data-needs.
 
 
 
 
 
 
 
Stores the locally required information about a data need of a permission.
 
 
 
 
 
 
 
 
 
 
 
Represents a permission request that is sent to an AIIDA instance
Repository for selecting the aggregate permission request by using the SQL view.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Service for handling exceptions thrown during API calls to Energinet
 
 
 
 
 
 
 
 
 
 
 
The main configuration for the EDA region connector.
 
 
 
 
 
 
 
The repository for PermissionRequests.
 
 
Serializes and deserializes the AttributeError to a JSON list in order to persist it to a database column.
 
 
 
 
 
 
 
 
 
This class encapsulates the data needed to request authorization from a NIF (User).
 
 
 
 
 
 
 
 
 
 
 
 
 
Response DTO for ETA Plus Auth token exchange.
 
 
This is the base class for CIM formatter strategies.
 
 
Intended to be used in combination with CustomValidationsGroup in GroupSequence annotation and be applied to basic constraints like NotNull.
 
 
 
 
 
 
 
 
 
 
 
 
 
A specialized class for ccmo-requests.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
This data need is used to request the addition of a metering point to an already existing Collective Energy Sharing Unit (CESU).
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Strategy interface to create a version-specific CIM RTD Envelope
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
The intent of this class is to abstract the Future Data polling procedure of each individual Region Connector.
Configuration for the CIM.
The supported versions of the CIM
 
 
 
A service that is used to request validated historical data for retransmission requests
 
 
 
 
Represents a generic status message for a permission
 
Subscribes to all events of an EventBus and creates connection status messages based on an event.
 
 
 
 
 
 
 
 
 
 
 
 
 
This class represents the contract details returned by the Datadis API.
 
 
 
 
 
 
This service routes retransmission messages between the region connectors.
 
 
 
 
 
 
 
CPRequestCR This can be used to request retransmission of consumption records in the specified timeframe
 
 
CPRequestResult, the enum represents the ResponseCodes described in the CR_REQ_PT process
 
 
 
 
 
 
 
Event emitted when a new permission request is created.
 
 
 
 
 
DTO returned after a permission request is successfully created.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
For validations that depend on other validations to be executed beforehand (e.g.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Used to by a region-connector to calculate start and end data of a data need, as well as reporting if it supports a certain data need.
Implementation of the DataNeedCalculationService that can be customized to fit the requirements of the region connector.
The DataNeedCalculationServiceRegistrar will be added to each region connector's own context and will register the DataNeedCalculationService of each region connector to the common DataNeedCalculationRouter.
 
 
 
 
 
 
 
 
 
 
 
This interface is used by the region connectors to specify the supported configurations of data needs.
The AccountingPointDataNeedRule specifies one supported variant of the AccountingPointDataNeed.
If this rule is present in a DataNeedRuleSet the region connector supports multiple data needs for creating permission requests.
The CESUJoinRequestDataNeedRule specifies that the region connector supports CESUJoinRequestDataNeed.
The InboundAiidaDataNeedRule specifies one supported variant of the AiidaDataNeed.
The OutboundAiidaDataNeedRule specifies one supported variant of the AiidaDataNeed.
This interface is used by the region connector to specify supported data need types and its configurations.
The ValidatedHistoricalDataDataNeedRule specifies one supported variant of the ValidatedHistoricalDataDataNeed.
This interface specifies all data need rules that are supported by a certain region connector.
The DataNeedRuleSetRegistrar will be added to each region connector's own context and will register the DataNeedRuleSet of each region connector to the common DataNeedRuleSetRouter.
 
 
DataNeedService that reads data needs from a JSON file.
 
 
 
 
 
 
 
 
Service interface for retrieving data needs.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Information about the data source such as the country code, the region connector id, the metered data administrator id and the permission administrator id.
 
 
 
 
 
 
 
 
 
 
 
 
 
Data source information for the German (DE) ETA Plus region connector.
CIM v0.82 Accounting Point provider for the German ETA Plus connector.
Spring configuration for the German (DE) ETA Plus region connector.
Configuration for the German (DE) ETA Plus region connector.
 
 
 
Main Spring Boot Application configuration for the German (DE) ETA Plus region connector.
 
 
 
 
 
 
 
 
JPA repository for permission events in the German (DE) region connector.
Permission request implementation for Germany (ETA Plus).
Repository interface for DePermissionRequest.
JPA Persistence configuration for the German (DE) ETA Plus region connector.
 
 
CIM v0.82 Validated Historical Data provider for the German ETA Plus connector (backwards compatible).
CIM v1.04 Validated Historical Data provider for the German ETA Plus connector.
 
 
 
 
Enum representing the distributor codes as defined in the Datadis API.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
This class is for processing incoming master data by mapping it to AccountingPointEnvelope
This interface defines the methods that must be provided by classes that facilitate the communication with EDA.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
A custom PermissionTimeframeStrategy that differentiates between energy community data needs and all others.
 
 
 
 
 
This class is for processing incoming consumption records by mapping it to ValidatedHistoricalDataMarketDocuments and emitting it for all matching permission requests
 
Record holding the description of an error that occurred when an API of EDDIE was called.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
The main configuration for the Enedis region connector.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
The main configuration for the Energinet region connector.
 
 
 
 
 
 
 
 
 
Class containing the possible response status codes from the Energinet API.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Accepted event for AccountingPointDataNeeds
Accepted event for ValidatedHistoricalDataNeeds
 
 
 
 
 
Implementation of the ESMP DateTime.
Implementation of the ESMP Time Interval.
 
 
 
 
 
 
 
 
 
 
Deserialised payload of the accounting-point response from the ETA+ backend.
 
 
Client for the ETA Plus API.
 
Exceptions thrown by EtaPlusApiClient during API communication with the ETA Plus system.
Thrown when the ETA Plus API responds with HTTP 401 or 403 due to invalid credentials.
Thrown when the ETA Plus API response body cannot be deserialized into the expected DTO.
Thrown when the ETA Plus API responds with HTTP 400 (Bad Request).
Thrown when the ETA Plus API responds with HTTP 403 (Forbidden) on a resource the bearer should normally authorise.
Thrown when the ETA Plus API responds with HTTP 404 (Not Found) for a requested resource.
Thrown when the ETA Plus API responds with a 5xx server error.
Thrown when the HTTP request to ETA Plus times out (connect or response timeout).
Metered data fetched from the ETA Plus historical-readings endpoint for a single metering point.
One reading element from the ETA Plus historical-readings response.
 
Thrown when persisting an event to the outbox fails.
Thrown when the ETA Plus API response cannot be mapped to the domain model.
Thrown when a permission request cannot be found in the DE-ETA repository.
Thrown when the ETA Plus API responds with HTTP 429 (Too Many Requests).
Shared wire-string-to-CIM mappings used by both v0.82 and v1.04 intermediate VHD documents.
Main Region Connector implementation for Germany (ETA Plus).
Metadata for the ETA Plus (Germany) region connector.
 
 
Interface for a simple EventBus implementation.
 
The interface for event handlers.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Contains all currently possible Granularities supported by at least one region connector.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Headers that can be used by outbound-connectors.
 
 
 
Registry that adds all health indicators from child contexts to the parent health indicator contributor registry.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Interface for all the classes that have a permission request and a payload, such as IdentifiableMeterReading.
 
 
 
 
Record that pairs a permission request with its corresponding validated historical data payload.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Exceptions which may indicate that some configurations are missing or invalid.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
A marker interface to differentiate between events that should be propagated to the eligible party.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Replacement for the JacksonJsonFormatMapper which only works for Jackson2 and not Jackson3.
 
 
 
A MessageSerde that serializes to JSON.
 
 
 
Wrapper class to avoid having to add JOSE dependencies to a module just to be able to catch a JOSEException.
 
 
 
 
 
 
 
 
 
 
Contains the data of an AiidaRecord
 
Internal event used to track the latest meter reading for a permission request.
Event handler that checks for fulfillment when the latest meter reading is updated.
 
 
 
 
 
 
 
 
 
 
 
 
Event emitted when a permission request is malformed (validation failed).
 
 
This Spring Configuration modifies the embedded webserver by opening a second port for the management api.
 
 
 
 
 
 
 
 
 
 
 
 
 
A component that can convert the measurement of a validated historical data market document.
 
 
 
 
 
 
This class contains the message code for the various messages we receive / send to EDA.
 
 
 
Requests for Energy communities.
 
 
 
 
 
 
A serde is a SERializer-DEserializer, which supports one or multiple formats to serialize and deserialize objects to and from.
Annotation used for marking methods to indicate that they process or interact with a specific type of message stream.
 
A centralized hub for managing message streams between providers and receivers.
 
 
 
 
 
 
 
The MetadataServiceRegistrar should be added to each region connector's own context and will register the RegionConnector of each region connector to the common MetadataService.
 
 
 
 
 
 
This class represents the metering data returned by the Datadis API.
Filter metering data by permission request start and end date to ensure only the requested data is returned.
Represents all the data needed to request metering data from Datadis.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
A permission request that stores date information about the latest meter reading that was pulled or received.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
A min-max envelope connector allows the eligible party to send reference energy curve min-max operating envelopes to a certain region-connector.
 
This service routes min-max envelope messages between the region connectors.
The MinMaxEnvelopeRouterRegistrar should be added to each region connector's own context and will register the RegionConnector of each region connector to the common MinMaxEnvelopeRouter.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
The model is only used to define the simulation scenarios, but are never created during runtime.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
This event is only used for the internal polling mechanism.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Mapping for all processes steps and message codes for the CMNotification.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
This configuration should be used to override the object mapper that is passed to the child instances from the core parent context.
 
 
 
Represents the JSON that is received from the Oesterreichs Energie Smart Meter Adapter.
 
 
 
 
 
 
 
 
 
An opaque envelope connector allows the eligible party to send opaque envelopes with any payload to a certain region-connector.
 
This service routes opaque envelopes between the region connectors.
The OpaqueEnvelopeRouterRegistrar should be added to each region connector's own context and will register the RegionConnector of each region connector to the common OpaqueEnvelopeRouterRegistrar.
 
Adds the OpenAPI documentation URLs of all enabled region connectors to the OpenAPI documentation in the current context, so that they can be accessed in the "Select a definition" drop down menu.
 
 
 
Denotes a class as an outbound-connector.
Annotation that indicates that the annotated class should be included in each context of a region connector.
 
Annotation, that allows Outbound Connectors to define a SecurityFilterChain.
 
 
Implementation of the outbox pattern.
 
 
 
 
 
 
This data transfer object is expected by the updatePermission API endpoint.
 
 
 
 
Permission control signal sent by the eligible party to a certain region connector.
 
Enables or disables transmission for a permission.
Terminates a permission, causing the region connector to stop transmitting data for it and clean up any associated resources.
Adjusts the transmission schedule for a permission.
 
A permission command connector allows the eligible party to send permission commands to a certain region-connector.
 
This service routes permission commands between the region connectors.
The PermissionCommandRouterRegistrar should be added to each region connector's own context and will register the RegionConnector of each region connector to the common PermissionCommandRouterRegistrar.
Handles PermissionCommands that the EP sends to a streamer.
 
 
 
 
 
 
 
 
 
 
 
 
The PermissionEventRepositoryRegistrar should be added to each region connector's own context and will register the PermissionEventRepository of each region connector to the common PermissionEventService.
 
 
 
 
 
 
 
This class converts a PermissionEvent to a CIM compliant document and provides them via a Flux.
 
 
 
 
Thrown to indicate that no permission with the specified ID is saved in this AIIDA instance.
 
 
Implements the status of the Permission Process Model.
 
A PermissionRequest represents the starting point of requesting the permission for data from an MDA.
 
 
 
 
 
 
 
REST controller for handling permission request creation for the German (DE) ETA Plus region connector.
 
 
 
 
 
 
 
 
 
Service for creating permission requests for the German (DE) ETA Plus region connector.
 
 
 
 
 
DTO for creating a new permission request for the German (DE) ETA Plus region connector.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Base class for persistable permission events in the German (DE) region connector.
 
 
 
 
 
 
 
 
 
 
 
Used to poll validated historical data.
 
 
Polls validated historical data from the ETA Plus API for active permission requests.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
This record defines all information needed for a PontonXPAdapter to establish a connection to a Ponton XP Messenger.
 
 
 
 
 
 
 
A record that holds the raw data as directly received from the MDA and some metadata information.
Factory for creating RawDataMessage instances
 
 
 
 
 
 
 
 
 
 
 
 
 
This annotation allows the core to find region connector implementations during classpath scanning.
A region connector connects MDAs to EDDIE.
The RegionConnectorConnectorElementProvider creates an HTTP GET mapping for the connector element javascript file for each individual region connector.
 
Annotation that indicates that the annotated class should be included in each context of a region connector.
 
 
Metadata for a RegionConnector.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Wraps the request in a cached request, since it is not able to get the request body twice.
 
 
 
This record represents a response code from EDA in the context of "Consent Management".
This enumeration contains all well known response codes with description that might be returned by a DSO in Austria.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
A retransmission connector allows the eligible party to request retransmission of data for a specific timeframe from a region-connector.
 
 
 
 
 
 
 
 
 
The RetransmissionRouterRegistrar should be added to each region connector's own context and will register the RegionConnectorRetransmissionService of each region connector to the common CoreRetransmissionRouter.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Representation of the functional blocks used by the green button
 
 
 
 
 
 
This class provides methods that create a security config for region-connectors that require a manuel response by the final customers.
 
 
 
 
 
Factory to create MessageSerde instances.
 
 
 
 
 
 
 
 
 
 
Using this annotation on a class or interface of a Bean that is instantiated in a child context causes the same Bean instance to be registered in the parent context as well.
BeanPostProcessor that checks for all beans whether it (or any ancestor interfaces of the Bean) is annotated with Shared.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Simple permission event for the German (DE) region connector.
 
 
 
 
 
 
 
 
 
 
The simulation context contains information, which is not available during the Model creation, but during the runtime phase.
 
 
 
 
The simulation engine is used to execute test simulations.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Internal event used to trigger polling for future data.
 
 
 
 
 
 
 
 
 
 
 
 
 
Defines a single step in a scenario.
 
The StreamerManager manages the lifecycle of AiidaStreamer.
Registrar for stream providers and suppliers within a Spring application context.
 
 
 
 
This class represents the supply data returned by the Datadis API.
 
 
 
DTO used to represent the supported dataNeeds for a specific regionConnectorId
 
 
Overwrites the SwaggerController path to consider the url mapping of a DispatcherServlet, instead of always using the same URL.
 
 
This handler terminates all permissions that are not needed anymore.
A termination connector receives permission market documents, which are intended to terminate an already accepted permission request.
 
 
 
 
This service routes termination messages between the region connectors.
The TerminationRouterRegistrar should be added to each region connector's own context and will register the RegionConnector of each region connector to the common TerminationRouter.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Configuration to set the timeouts of permission requests.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Utility class to track different document types that can be consumed or produced by eddie
All the supported data models
The recipient of a specific document.
The document types that can be consumed or produced by eddie.
This exception indicates that a connection or transmission error occurred.
 
 
 
 
 
 
 
 
Class to differentiate between the unit types, since they are grouped together.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Used to indicate that the authorization was updated and should include meters now.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Event emitted when a permission request is validated.
 
 
 
 
 
 
A data need designed to request validated historical data from the MDA.
Result type for the calculation of validated historical data data-needs.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Central stream for validated historical data from ETA Plus.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
A MessageSerde implementation that produces CIM compliant XML.