[
https://issues.apache.org/jira/browse/OLINGO-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13809158#comment-13809158
]
Stephan Klevenz commented on OLINGO-50:
---------------------------------------
There are two options:
1) Use configuration in isDebugEnabled() to switch the feature on/off
2) There is another callback interface you can implement and register within
the service factory. It is named ODataErrorCallback. While implementing this
you can use your own log api.
FullAck to documentation. Let's keep this issue open until everything is
documented.
> Exceptions are not throw
> ------------------------
>
> Key: OLINGO-50
> URL: https://issues.apache.org/jira/browse/OLINGO-50
> Project: Olingo
> Issue Type: Bug
> Components: odata2-documentation
> Affects Versions: 1.0.0
> Reporter: Thiago Assis
> Assignee: Stephan Klevenz
>
> I cant see the stack trace of the generated exception, is not generated in te
> application server log and the browser returns
> <?xml version='1.0' encoding='UTF-8'?><error
> xmlns="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata";><code/><message
> xml:lang="en-US">An exception occurred.</message></error>
> This happen when i request the URL: http://localhost:8888/odata/
--
This message was sent by Atlassian JIRA
(v6.1#6144)
