Post by asmithakr on Mar 9, 2021 9:32:17 GMT
Hi All,
I have been having a confusion on the error response format that is sent back to the client in case of any error.
As per section 9.6 of www.dmtf.org/sites/default/files/standards/documents/DSP0266_1.11.1.pdf, any error should contain an "error" property which contains three properties:
But in sections 10.8.2.1 and 10.8.2.2, i see that both extended object information and extended property information's example doesnt have "error" property instead they were just displayed as @message.ExtendedInfo and "PinOut@Message.ExtendedInfo" respectively.
The way 10.8.2.* displays error response:
The way i hope it must be displayed:
Is there a conflict in the specification between those two sections (9.6 and 10.8.2.*)?
I was wondering should the example snippet under sections 10.8.2.* display the extendedInfo within the "error" property as mentioned in 9.6 (like the above).
Could someone clarify on this?
Thanks in advance!
I have been having a confusion on the error response format that is sent back to the client in case of any error.
As per section 9.6 of www.dmtf.org/sites/default/files/standards/documents/DSP0266_1.11.1.pdf, any error should contain an "error" property which contains three properties:
- @message.ExtendedInfo
- code
- message
But in sections 10.8.2.1 and 10.8.2.2, i see that both extended object information and extended property information's example doesnt have "error" property instead they were just displayed as @message.ExtendedInfo and "PinOut@Message.ExtendedInfo" respectively.
The way 10.8.2.* displays error response:
{
.
.
.
"PinOut@Message.ExtendedInfo": [
{
"MessageId": "Base.1.8.PropertyValueNotInList",
"Message": "The value Contoso for the property PinOut is not in the list of acceptable values.",
"Severity": "Warning",
"MessageSeverity": "Warning",
"Resolution": "Choose a value from the enumeration list that the implementation can support and resubmit the request if the operation failed."
}
]
}
.
.
.
"PinOut@Message.ExtendedInfo": [
{
"MessageId": "Base.1.8.PropertyValueNotInList",
"Message": "The value Contoso for the property PinOut is not in the list of acceptable values.",
"Severity": "Warning",
"MessageSeverity": "Warning",
"Resolution": "Choose a value from the enumeration list that the implementation can support and resubmit the request if the operation failed."
}
]
}
{
.
.
.
"error": {
"PinOut@Message.ExtendedInfo": [
{
"MessageId": "Base.1.8.PropertyValueNotInList",
"Message": "The value Contoso for the property PinOut is not in the list of acceptable values.",
"Severity": "Warning",
"MessageSeverity": "Warning",
"Resolution": "Choose a value from the enumeration list that the implementation can support and resubmit the request if the operation failed."
}
],
"code":"...",
"message":"..."
}
.
.
.
"error": {
"PinOut@Message.ExtendedInfo": [
{
"MessageId": "Base.1.8.PropertyValueNotInList",
"Message": "The value Contoso for the property PinOut is not in the list of acceptable values.",
"Severity": "Warning",
"MessageSeverity": "Warning",
"Resolution": "Choose a value from the enumeration list that the implementation can support and resubmit the request if the operation failed."
}
],
"code":"...",
"message":"..."
}
Is there a conflict in the specification between those two sections (9.6 and 10.8.2.*)?
I was wondering should the example snippet under sections 10.8.2.* display the extendedInfo within the "error" property as mentioned in 9.6 (like the above).
Could someone clarify on this?
Thanks in advance!
