[
https://issues.apache.org/jira/browse/OLINGO-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Amend resolved OLINGO-339.
------------------------------------
Resolution: Fixed
Fixed with this commit:
https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=2340c023da02512c574a17dd5954caf674f8dd4f
> 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
> Assignee: Christian Amend
> Priority: Minor
> Labels: behavior
> Fix For: V2 2.0.1
>
>
> 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.3.4#6332)
