[
https://issues.apache.org/jira/browse/OLINGO-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bolz resolved OLINGO-196.
---------------------------------
Resolution: Fixed
With last commit ({{1f37db3e9b84f074bf9450cc2c7565ccb3fc9cf1}}) this feature is
implemented.
[~sumiteshrs]: It would be nice if you can take a look and test the feature and
give feedback.
Kind regards,
Michael
{code}
[OLINGO-196] Added tests and improved innerError handling (XML/JSON)
Project: http://git-wip-us.apache.org/repos/asf/olingo-odata2/repo
Commit: http://git-wip-us.apache.org/repos/asf/olingo-odata2/commit/1f37db3e
Tree: http://git-wip-us.apache.org/repos/asf/olingo-odata2/tree/1f37db3e
Diff: http://git-wip-us.apache.org/repos/asf/olingo-odata2/diff/1f37db3e
{code}
> A means should be exposed for de-serializing error streams
> ----------------------------------------------------------
>
> Key: OLINGO-196
> URL: https://issues.apache.org/jira/browse/OLINGO-196
> Project: Olingo
> Issue Type: New Feature
> Components: odata2-core
> Affects Versions: V2 1.0.0, V2 1.1.0
> Reporter: Sumitesh R S
> Assignee: Michael Bolz
> Priority: Critical
> Fix For: V2 1.3.0
>
>
> Currently, there is no means exposed to interpret error streams and get the
> translated error message when a service request returns error. It would be
> good if a means is exposed in EntityProvider which takes the error stream and
> returns a error message document back. Also, in order to make
> org.apache.olingo.odata2.api.commons.HttpStatusCodes consumable from the
> clients, it would be good if a means is exposed to take the response code as
> input which gives back a translated status definition back.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
