You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "Michael Bolz (JIRA)" <ji...@apache.org> on 2016/02/13 07:00:21 UTC
[jira] [Assigned] (OLINGO-856) ODataHandler like interface in core
API
[ https://issues.apache.org/jira/browse/OLINGO-856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Bolz reassigned OLINGO-856:
-----------------------------------
Assignee: Michael Bolz
> ODataHandler like interface in core API
> ---------------------------------------
>
> Key: OLINGO-856
> URL: https://issues.apache.org/jira/browse/OLINGO-856
> Project: Olingo
> Issue Type: New Feature
> Components: odata4-server
> Affects Versions: (Java) V4 4.1.0
> Reporter: Michael Bolz
> Assignee: Michael Bolz
> Priority: Minor
>
> If Olingo will be used in a none Java Servlet environment it is complicated to do this because of the {{void process(HttpServletRequest request, HttpServletResponse response);}} entry point which is dependent on the servlet request/response objects.
> To avoid this a interface with a {{process}} method like in the {{org.apache.olingo.server.core.ODataHandler}} with the {{ODataRequest}} and {{ODataResponse}} objects would be better.
> This intercase also should be the result of the {{OData.createHandler(ServiceMetadata serviceMetadata):ODataHttpHandler}} method.
> This would help a lot to use Olingo in other web frameworks (beside of the Java Servlet).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)