You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "Peter Rilling (JIRA)" <ji...@apache.org> on 2016/05/21 21:51:13 UTC
[jira] [Created] (OLINGO-958) Inner exceptions are lost when
sending error message in batch request.
Peter Rilling created OLINGO-958:
------------------------------------
Summary: Inner exceptions are lost when sending error message in batch request.
Key: OLINGO-958
URL: https://issues.apache.org/jira/browse/OLINGO-958
Project: Olingo
Issue Type: Improvement
Components: odata2-core
Affects Versions: V2 2.0.6
Reporter: Peter Rilling
Normally when an exception happens, that message is written to the response. I have noticed that if there are inner exceptions, those messages get lots.
My particular scenario is where we are using JPA/Eclipselink to provide the data. If we are sending a changeset, and something happens like a constraint violation, that gets wrapped in a RollbackException.
For this, you get a message about a RollbackException happening, but no info on the inner exception (such as what actually happened). If I don't use a batch to make a change, and the error occurs, I get see the actual message.
I got around this by configuration Eclipselink to write to our log file, but it would be nice to have the full set of messages to be written to the response.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)