[
https://issues.apache.org/jira/browse/OLINGO-856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15147815#comment-15147815
]
Michael Bolz commented on OLINGO-856:
-------------------------------------
Hi [~rareddy],
I pushed a _proposal_ to the feature brunch (see [this
commit|https://git1-us-west.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=febf6ed5cfc24392627cb27f6c0962ab79089d4d].
Is would be nice if you can have take a look at it and give feedback.
A change to the before discussion was to remove the generics and have only the
interface:
{code}
void register(OlingoExtension extension);
{code}
Additional I moved the already existing {{register(...)}} method to to
{{ODataHttpHandler}} so that the {{ODataHandler}} only have one register method
(the {{ODataHttpHandler}} keep the _old_ methods for backward compatibility).
Kind Regards, Michael
> 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 interface 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)
