11. Exception Structure
The messaging-services can return many different exceptions. Following is a list of the most important exceptions and their meanings:
| Exception | Since Version | Service-Module (Domain) | Interpretation |
|---|---|---|---|
| ConfigUpdateException | 4.1.0.0 | Core (Configuration) | Exception that is thrown, when an error occurs while trying to change the configuration. |
| ClaimsException | 4.1.0.0 | Core (DAPS) | Exception that gets thrown, if errors occur while validating a DAT token. |
| ConnectorMissingCertExtensionException | 4.1.0.0 | Core (DAPS) | Exception that is thrown, when an Extension (aki, ski) of the cert is missing. -> DAPS Token can not be acquired. |
| DapsConnectionException | 4.1.0.0 | Core (DAPS) | Exception is thrown if communication to the DAPS fails. For example, if the DAPS URL is incorrect or other connection problems to the DAPS occur. -> DAPS Token can not be acquired. |
| DapsEmptyResponseException | 4.1.0.0 | Core (DAPS) | Exception which is thrown when the Response from the DAPS is empty and can't be processed further. -> DAPS Token can not be acquired. |
| DapsTokenManagerException | 4.1.0.0 | Core (DAPS) | Superclass of ConnectorMissingCertExtensionException, DapsConnectionException and DapsEmptyResponseException. Can be caught instead of them. -> DAPS Token can not be acquired. |
| ValidationRuleException | 4.1.1.0 | Core (DAPS) | Custom Validation rules exception, exception which is thrown by custom DatValidationRule evaluation. |
| MessageBuilderException | 4.2.0.0 | Messaging (Sending Message) | An exception that is thrown if building an IDS-Message with the given information threw a ConstraintViolationException (catches builders RuntimeException). |
| SerializeException | 4.2.0.0 | Messaging (Sending Message) | An exception that is thrown if serializing a message using the IDS-Serializer threw an IOException. Could indicate missing required message-fields. |
| URISyntaxException | 4.2.0.0 | Messaging (Sending Message) | If the URL of the target is not a valid URI. |
| SendMessageException | 4.2.0.0 | Messaging (Sending Message) | If sending the IDS-Request returns an IOException. Recipient not reachable or other further problems. |
| PreDispatchingFilterException | 4.1.0.0 | Messaging (Receiving Message) | Exception that is thrown when an error occurs during preprocessing of incoming headers with a PreDispatchingFilter. In PRODUCTIVE_DEPLOYMENT this would be for example the check of the DAT of the incoming message, which can report an error. |
| DeserializeException | 4.2.0.0 | Messaging (Receiving Message) | An exception that is thrown if deserializing a message using the IDS-Serializer threw an IOException. Could indicate a non-valid IDS-Message. |
| ShaclValidatorException | 4.2.0.0 | Messaging (Receiving Message) | SHACL-Validation, received message header does not conform to IDS-Infomodel and did not pass SHACL-Validation. (SHACL-Validation can be truned off) |
| UnknownResponseException | 4.2.0.0 | Messaging (Receiving Message) | An exception that is thrown during converting an IDS-Response into a corresponding Object if no possible cast found. Could indicate a new unknown IDS-Message-Type. Error which is caused internally, but is passed on. |
| UnexpectedResponseException | 4.2.0.0 | Messaging (Receiving Message) | An exception that is thrown after converting a Response into the corresponding Object if the received response-type is not expected as a response to the request send. |
Furthermore, there are exceptions, such as the IOException, which are used for all other error cases that are not specific to the messaging-services.