Difference between revisions of "Extensions.DiagCom.UnknownResponseException"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
{{DISPLAYTITLE:Exception '''UnknownResponseException'''}} | {{DISPLAYTITLE:Exception '''UnknownResponseException'''}} | ||
== Classification == | == Classification == | ||
| − | {{ClassificationException | UnknownResponseException | [[Core.DataTypes.ComplexDataType|Complex Data Type]] |[[Extensions.DiagCom.DiagComException|DiagComException]]}} | + | {{ClassificationException | UnknownResponseException | [[Core.DataTypes.ComplexDataType|Complex Data Type]] |[[Extensions.DiagCom.DiagComException|DiagComException]]| {{OtxSpec3}} }} |
== Description == | == Description == | ||
This exception is thrown in case execution of a diagnostic service returned a response that was not mapped by the [[Extensions.DiagCom.ExecuteDiagService|ExecuteDiagService]] action. If no <responseParameters> are defined, no '''UnknownResponseException''' will be thrown. | This exception is thrown in case execution of a diagnostic service returned a response that was not mapped by the [[Extensions.DiagCom.ExecuteDiagService|ExecuteDiagService]] action. If no <responseParameters> are defined, no '''UnknownResponseException''' will be thrown. | ||
Revision as of 03:10, 12 September 2019
Classification
| Name | UnknownResponseException |
| Class | Complex Data Type |
| Base Data Type | DiagComException |
| SpecifiedBy | ISO 13209-3 |
Description
This exception is thrown in case execution of a diagnostic service returned a response that was not mapped by the ExecuteDiagService action. If no <responseParameters> are defined, no UnknownResponseException will be thrown.
