You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "Stephan Klevenz (JIRA)" <ji...@apache.org> on 2014/07/04 12:23:34 UTC

[jira] [Updated] (OLINGO-339) Servlet behaviour on null ODataService

     [ https://issues.apache.org/jira/browse/OLINGO-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stephan Klevenz updated OLINGO-339:
-----------------------------------

    Fix Version/s: V2 2.1.0

> Servlet behaviour on null ODataService
> --------------------------------------
>
>                 Key: OLINGO-339
>                 URL: https://issues.apache.org/jira/browse/OLINGO-339
>             Project: Olingo
>          Issue Type: New Feature
>          Components: odata2-core
>    Affects Versions: V2 1.2.0
>            Reporter: Jonathan Bayle
>            Priority: Minor
>              Labels: behavior
>             Fix For: V2 2.1.0
>
>
> When the method ODataServiceFactory.createService returns null, the
> servlet throws an uncaught NullPointerException which has to be handled
> by the servlet container.
> In my opinion, the servlet should print an error message like "service not
> found", it would be better if the message is wrapped in an OData error
> document.
> Maybe an implementation of ODataService could perform this ?



--
This message was sent by Atlassian JIRA
(v6.2#6252)