[
https://issues.apache.org/jira/browse/OLINGO-599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sachin C updated OLINGO-599:
----------------------------
Comment: was deleted
(was: Hi Chandan,
I checked the only service factory method we have but there was no such method
as setDetailedError(bool). Can you tell exactly which is this class where we
need to set it.
Also I debugged the Olingo code where the exception is thrown, I did not see
any conditional check for boolean value before forming the error messages. What
I did see is that you get the 2 error messages, 1 Simple one and other the more
complex one.
You also pass these to a format(String,args) method but it does not change
anything at least in out situation. The simple error itself is thrown. Can you
please clarify this?
Thanks,
Sachin)
> Improvement in error messages.
> ------------------------------
>
> Key: OLINGO-599
> URL: https://issues.apache.org/jira/browse/OLINGO-599
> Project: Olingo
> Issue Type: Improvement
> Components: odata2-jpa
> Affects Versions: V2 2.0.2, V2 2.0.3
> Environment: Olingo JPA used in Integration Gateway
> Reporter: Sachin C
> Fix For: V2 2.0.4
>
> Original Estimate: 336h
> Remaining Estimate: 336h
>
> Hi,
> This is regarding the error messages thrown from the Olingo JPA side when
> there is a failure due a wrong payload or something like that. For now the
> error messages are all of the form
> "OData JPA " METHOD "syntax is not correct.
> Where METHOD can be CREATE,DELETE,UPDATE etc. What we want is a more clear
> error as to what went wrong such as "So and so constraint is violated " or
> any statement which is more specific regarding the cause of the error.
> Thanks,
> Sachin
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
