[
https://issues.apache.org/jira/browse/OLINGO-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13809090#comment-13809090
]
Georgi commented on OLINGO-50:
------------------------------
So how do you support your application by tracing and analyzing execution log
for a past period of time? You don't expect people to go productive with a
mandatory odata-debug=json query parameter, do you?
> Exceptions are not throw
> ------------------------
>
> Key: OLINGO-50
> URL: https://issues.apache.org/jira/browse/OLINGO-50
> Project: Olingo
> Issue Type: Bug
> 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)
