class ara::rds::RdsErrorDomain

The error domain ara::rds::RdsErrorDomain identifies and categorizes specific error states of the Raw Data Stream module according to AUTOSAR_AP_SWS_RawDataStream §1 “Raw Data Stream”. It provides associated error message texts and allows throwing errors as exceptions [SWS_RDS_11296]. Because the default constructor is deleted [SWS_RDS_11294], applications access the central instance via the free function GetRdsErrorDomain() [SWS_RDS_11298].

more ›

Context

The class ara::rds::RdsErrorDomain represents the specific error domain for the Raw Data Stream (RDS) functional cluster on the Adaptive Platform AUTOSAR_AP_SWS_RawDataStream §1 “Raw Data Stream”. As a specialization of the base class ara::core::ErrorDomain, it integrates stream-related error states into the platform-wide error handling model of AUTOSAR. Core responsibilities of the class include providing a unique domain name via the Name() method [SWS_RDS_11295] and mapping error codes to meaningful diagnostic messages using Message() [SWS_RDS_11296].

For consistent handling in client code, the domain defines standardized type aliases: The alias Errc refers to the enumeration RdsErrc [SWS_RDS_11326], while the type alias Exception is bound to the exception type RdsException [SWS_RDS_11327]. Interaction partners primarily include application components, streaming endpoints, and the infrastructure types ara::core::ErrorCode and ara::core::Result, which use the error domain to identify encountered errors.

Lifecycle

Instances of ara::rds::RdsErrorDomain are subject to a strictly controlled lifecycle. Direct instantiation by client code is explicitly prevented because the default constructor is deleted (=delete) [SWS_RDS_11294]. Instead, access is realized via the global helper function GetRdsErrorDomain(), which returns a constant reference to the domain [SWS_RDS_11298].

Interpretation: The error domain is likely implemented as a long-lived singleton that exists throughout the entire execution duration of the process. Question (open) Because all querying interfaces such as Name() [SWS_RDS_11295] and Message() [SWS_RDS_11296] are declared as const as well as noexcept, thread-safe concurrent read access by multiple threads is possible without synchronization overhead.

Usage Path

The typical usage path occurs as soon as an operation of the Raw Data Stream fails and a corresponding error object must be analyzed or propagated. An application or middleware layer typically receives an error object bound to the domain or references the domain directly via GetRdsErrorDomain() [SWS_RDS_11298]. The associated text of the error code can be queried at runtime via the Message() method and logged in log outputs [SWS_RDS_11296].

If the error handling strategy of the application is based on C++ exceptions, the ThrowAsException() method is called [SWS_RDS_11297]. This transforms the passed ara::core::ErrorCode into an exception of type RdsException specified via the type alias Exception [SWS_RDS_11327].

Sequence diagram: Typical flow of error handling and exception throwing via the Raw Data Stream error domain. Sources: [SWS_RDS_11296], [SWS_RDS_11297], [SWS_RDS_11298]

Error Scenarios

In the context of the error domain itself, no exceptions occur during regular queries: The identification and localization methods Name() [SWS_RDS_11295] and Message() [SWS_RDS_11296] guarantee freedom from errors through their noexcept specification. The access function GetRdsErrorDomain() also never fails [SWS_RDS_11298].

The primary error scenario concerns exception handling: If a caller invokes ThrowAsException() with a valid ara::core::ErrorCode, the method does not terminate regularly, but mandatorily throws an exception (noexcept(false)) of type RdsException [SWS_RDS_11297]. A precondition for this call is passing a consistent error code from the domain; the postcondition is triggering the exception in the caller context for further handling in the corresponding catch block.