[ 
https://issues.apache.org/jira/browse/OLINGO-894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15188688#comment-15188688
 ] 

Michael Bolz commented on OLINGO-894:
-------------------------------------

Hello [~gira1],

No problem with the help and nice to hear that the _re-package_ worked for you.

{quote}
For the issue I have to admit that the whole JAX-RS related parts should all be 
in a separate maven module and not in the core library module.
However such a change (extraction of the JAX-RS from the core) would be a 
little bit tricky if the backward compatibility should be kept.
{quote}

Because that the IMHO only good solution for Olingo (see quote above) would 
require a major change (and have to be discussed) I will resolve/close this 
issue and have created OLINGO-899.

Hope this is ok for you, otherwise please re-open and comment.

Best Regards, Michael

> Olingo 2 hides all JEE7 execption handling
> ------------------------------------------
>
>                 Key: OLINGO-894
>                 URL: https://issues.apache.org/jira/browse/OLINGO-894
>             Project: Olingo
>          Issue Type: Bug
>          Components: odata2-core
>    Affects Versions: V2 2.0.6
>         Environment: JEE7 compliant application server. We use IBM WebSphere 
> Liberty 8.5.5.8.
>            Reporter: Hans Schuell
>            Assignee: Michael Bolz
>            Priority: Critical
>
> We are using "olingo-odata2-core" in a JEE7 application for parsing OData 
> filter expressions. Whenever a runtime exception in the application is not 
> catched, the Olingo component supresses all error information (cause, stack 
> trace, ...) and reduce the information to "Exception during error handling 
> occured!". This is very annoying and we always have to remove Olingo from the 
> build to get the real error.
> We have made a sample project to show this. See 
> https://github.com/giraone/olingo-bug. It is a totally simple JAX-RS 
> implementation, which does not use Olingo, but it has a dependency on it in 
> the pom.xml. This is sufficient to produce the problem. Please look at the 
> readme.md and run the simple test.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to