Package energy.eddie.regionconnector.at.eda.handlers.integration.inbound

Class CCMSHandler

java.lang.Object

energy.eddie.regionconnector.at.eda.handlers.integration.inbound.CCMSHandler

@Component
public class CCMSHandler
extends Object

Constructor Summary

Constructors

Constructor	Description
CCMSHandler(Outbox outbox, AtPermissionRequestRepository repository)

Method Summary

Modifier and Type	Method	Description
void	handleCCMSAnswer(CMRequestStatus cmRequestStatus)
void	handleCCMSReject(CMRequestStatus cmRequestStatus)	Handle a CCMS_REJECT message.

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Details

CCMSHandler

public CCMSHandler(Outbox outbox,
 AtPermissionRequestRepository repository)

Method Details

handleCCMSReject

public void handleCCMSReject(CMRequestStatus cmRequestStatus)

Handle a CCMS_REJECT message. We mark the permission request as externally terminated no matter the reason. This means even if we still receive data from the DSO we will not process it.

We do this, since the response codes ResponseCode.CmRevSP.NO_CONSENT_PRESENT and ResponseCode.CmRevSP.CONSENT_ID_EXPIRED both indicate that the consent is not valid anymore, so we should not receive any data anymore. This case should only occur if the eligible party tries to terminate a permission request that has already been PermissionProcessStatus.FULFILLED.

The response code ResponseCode.CmRevSP.INVALID_PROCESSDATE should never occur since we set the process date of the CCMORevoke to the current date.

The last option ResponseCode.CmRevSP.CONSENT_AND_METERINGPOINT_DO_NOT_MATCH should never occur, if this occurs we have a bug in our system.

handleCCMSAnswer

public void handleCCMSAnswer(CMRequestStatus cmRequestStatus)