class ara::rds::RdsException

The class ara::rds::RdsException represents the specialized exception type for the Raw Data Stream module and serves to propagate errors based on ara::core::ErrorCode [SWS_RDS_11292]. Instantiation typically occurs within error handling by ThrowAsException, which triggers a structured abort of the faulty sequence [SWS_RDS_11297]. The constructor declared as noexcept guarantees that no subsequent errors occur in the runtime system during the creation of the exception. Calling application code must catch the exception to prevent a program abort.

more ›

Context

In the context of AUTOSAR Adaptive, the class ara::rds::RdsException acts as a dedicated exception type for the Raw Data Stream (rds), as specified in SWS RawDataStream §1 “Raw Data Stream”. It derives directly from the general base class ara::core::Exception and seamlessly integrates the module's error model into the platform's exception handling. Within the RDS namespace, the type is provided via the type alias Exception [SWS_RDS_11327], which enables a uniform and simplified nomenclature for users and module components. Primary interaction partners include error domains such as the domain declared in ara/rds/rds_error_domain.h, as well as application code that handles errors via exceptions [SWS_RDS_11292].

Lifecycle

Instances of ara::rds::RdsException are created on demand as soon as an error event that occurred forces the abort of the regular control flow. Instantiation is performed via an explicit constructor that takes a ara::core::ErrorCode object [SWS_RDS_11292]. This constructor is declared as noexcept, which guarantees that object creation itself will under no circumstances fail or throw another exception. The exception object is subject to regular C++ value semantics: it is transferred to the exception storage of the runtime environment when thrown. As is customary for exception types in ara::core, the destruction time is likely tied to leaving the responsible catch block once the reference to the exception object expires. Question Q-5673ede6a9688b85 (open) In concurrent execution environments, the class behaves thread-safely, since each exception situation is instantiated and propagated in isolation at the thread-local level.

Usage Path

The typical usage path comprises detecting an error state during stream operation, converting the error code into an exception, and downstream catching in the application code. If an error occurs during an operation, it is primarily represented as ara::core::ErrorCode. Instead of a manual query, triggering the exception can be initiated via the method ThrowAsException, which encapsulates the conversion and the throwing process [SWS_RDS_11297]. Interpretation: The call to ThrowAsException presumably delegates internally directly to the constructor of RdsException and throws the newly created instance using throw [SWS_RDS_11292]. Question Q-d8734426a5c71e07 (open) The calling code catches the exception via the concrete type ara::rds::RdsException, the alias ara::rds::Exception [SWS_RDS_11327], or polymorphically via ara::core::Exception.

Sequence diagram: Interaction during throwing and catching an RDS exception via an ErrorCode. Sources: [SWS_RDS_11292], [SWS_RDS_11297].

Error Scenarios

Error scenarios surrounding ara::rds::RdsException primarily concern the consistency of error propagation and the avoidance of unhandled program aborts. The throwing operation ThrowAsException is explicitly defined as noexcept(false) [SWS_RDS_11297], since throwing the exception represents the intended behavior upon errors. A critical error scenario arises if calling code ignores the potential control flow abort and does not provide an appropriate exception handler; incomplete handling leads to an immediate abort of the process via std::terminate. However, the noexcept guarantee of the constructor [SWS_RDS_11292] ensures that no nested initialization error can occur during the provision of the exception itself.