[jira] [Resolved] (OLINGO-274) fix V4 json error response's deserializing (ATOM is still a TODO)

["Challen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OLINGO-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Challen resolved OLINGO-274.
----------------------------
    Resolution: Fixed

resolve tihs for Olingo client, since it is about ATOM payload, which is not the official support of OData V4 protocol, so should be low priority

> fix V4 json error response's deserializing (ATOM is still a TODO)
> -----------------------------------------------------------------
>
>                 Key: OLINGO-274
>                 URL: https://issues.apache.org/jira/browse/OLINGO-274
>             Project: Olingo
>          Issue Type: Bug
>          Components: odata4-client-JS
>    Affects Versions: V4 4.0.0-beta-01
>            Reporter: Challen
>            Assignee: Challen
>             Fix For: V4 4.0.0-beta-01
>
>
> V4 error is like: 
> {
>   "error": {
>     "code": "400",
>     "message": "Bad request.",
>     "target": "query",
>     "details": [
>       {
>        "code": "400",
>        "target": "$search" ,
>        "message": "Microsoft.Data.OData.BadRequest"
>       }
>     ],
>     "innererror": {
>       "trace": ["at Microsoft.Data.OData.MediaTypeUtils.GetContentTypeFromSettings....","callmethod2 etc"],
>       "context": {"key1":"for debug deployment only"}
>     }
>   }
> }
> ATOM part is not updated for V4 yet. but ATOM format is not official v4 standard, so is not a high priority. for now I keep this JIRA issue open just in case someone wants to fix it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)