Suggesting improvements to Olingo exception messages

[Kasun Eranga Kumarasinghe <ke...@gmail.com>]

Hi All,



Some Exception messages provided by Olingo are not that helpful when it
comes to debugging.

For example consider a scenario where an incompatible data value is used in
$filter system query option as follows.

http://localhost:8080/odata-server-tecsvc-4.6.0-SNAPSHOT/odata.svc/ESAllPrim?$filter=PropertyInt16%20eq%20%2732767%27&$format=application/json



For this request, the response is like this: "The types 'Edm.Int16' and
'Edm.String' are not compatible."

This exception message doesn’t indicate for which property in odata object
the data type incompatibility has occurred.

So if the request is more complex, then finding the exact mistake is very
hard.



Just want know if there are any plans on improving exception messages?


Best regards,

Kasun Kumarasinghe.

Re: Suggesting improvements to Olingo exception messages

[Ramesh Reddy <ra...@redhat.com>]

Open a JIRA with improvement request.

Ramesh..

On Fri, Aug 17, 2018 at 6:35 AM Kasun Eranga Kumarasinghe <
kerangak@gmail.com> wrote:

> Hi All,
>
>
>
> Some Exception messages provided by Olingo are not that helpful when it
> comes to debugging.
>
> For example consider a scenario where an incompatible data value is used
> in $filter system query option as follows.
>
>
> http://localhost:8080/odata-server-tecsvc-4.6.0-SNAPSHOT/odata.svc/ESAllPrim?$filter=PropertyInt16%20eq%20%2732767%27&$format=application/json
>
>
>
> For this request, the response is like this: "The types 'Edm.Int16' and
> 'Edm.String' are not compatible."
>
> This exception message doesn’t indicate for which property in odata object
> the data type incompatibility has occurred.
>
> So if the request is more complex, then finding the exact mistake is very
> hard.
>
>
>
> Just want know if there are any plans on improving exception messages?
>
>
> Best regards,
>
> Kasun Kumarasinghe.
>