[
https://issues.apache.org/jira/browse/OLINGO-856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15147830#comment-15147830
]
Ramesh Reddy commented on OLINGO-856:
-------------------------------------
You do not need the "register" methods on the "ODataHttpHandler" as it already
extends the "ODataHandler".
Actually thinking about this design again, I seems to favor, just with one
method
{code}
void register(Processor processor);
{code}
Then extend your _CustomContentTypeSupport_ and _CustomETagSupport_ with
_Processor_, that way those methods will a way to initialize themselves, and
there will be single register method. It will not break any other code, because
both these extensions are Olingo Framework's
> 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)
