You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "Ramya (JIRA)" <ji...@apache.org> on 2019/08/02 07:17:00 UTC
[jira] [Commented] (OLINGO-1380) OData V4: Response header
information is lost in case of exceptions
[ https://issues.apache.org/jira/browse/OLINGO-1380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16898636#comment-16898636 ]
Ramya commented on OLINGO-1380:
-------------------------------
This is fixed as part of the commit https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=e3650599007a917890963fbec6a19b437d519e4d
> OData V4: Response header information is lost in case of exceptions
> -------------------------------------------------------------------
>
> Key: OLINGO-1380
> URL: https://issues.apache.org/jira/browse/OLINGO-1380
> Project: Olingo
> Issue Type: Bug
> Reporter: Ramya
> Priority: Major
>
> Whenever an exception occurs in client scenarios we throw ODataClientErrorException with statusLine and ODataError. However, the response header information is lost.
> So have new API's in ODataClientErrorException to set and get header information.
> Also, currently if the response is in a Json format only then we can deserialize the entity and form ODataError.
> If the server returns the response as a plain text, then also make provision to include this information in ODataError object.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)