[jira] [Updated] (OLINGO-1363) Java 9+ support

2020-02-16 Thread Michael van der Gulik (Jira)
[ https://issues.apache.org/jira/browse/OLINGO-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael van der Gulik updated OLINGO-1363: -- Attachment: 0001-Add-the-Jakarta-XML-bindings-dependency-so-it-compil.patch >

[jira] [Commented] (OLINGO-1363) Java 9+ support

2020-02-16 Thread Michael van der Gulik (Jira)
[ https://issues.apache.org/jira/browse/OLINGO-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17037979#comment-17037979 ] Michael van der Gulik commented on OLINGO-1363: --- The 0001-Add-the-Jakarta.

Which Java version do we code against?

2020-02-16 Thread Michael van der Gulik
Hi. I was looking at improving the error handling because I just got a completely useless error message out of Olingo. I was looking at ODataHandlerImpl.java: } catch (final UriValidationException e) { ODataServerError serverError = ODataExceptionHelper.createServerErrorObject(e, null); hand

Re: Which Java version do we code against?

2020-02-16 Thread Michael van der Gulik
Also, what logging framework are you using? I'm not seeing any logging messages anywhere. Any exception without a message (in my case, NullPointerException) gets converted into a generic message (ODataExceptionHandler.java:163) and the whole exception is basically lost. Michael. On Mon, Feb 17,

Re: Which Java version do we code against?

2020-02-16 Thread Michael van der Gulik
I take that back. In pom.xml: 1.8 I need to engage my brain next time. Thanks, Michael. On Mon, Feb 17, 2020 at 10:45 AM Michael van der Gulik wrote: > Hi. > > I was looking at improving the error handling because I just got a > completely useless error message out of Olingo. > > I was lookin