[
https://issues.apache.org/jira/browse/OLINGO-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14200486#comment-14200486
]
Ramesh Reddy commented on OLINGO-450:
-------------------------------------
It is good in perspective that what is being returned makes it simple and
removes the serialization and context-url building responsibility from service
developer. Which is good. But we need to make sure that the context of the
query execution is also preserved. For example:
readEntityCollection
readEntity
can happen on either using Function/Action call or resource call, conveying how
it is being executed is also important IMO. Like instead of passing
OdataRequest, this could be done with derived types like ResourceOdataRequest
vs FunctionOdataRequest etc. that conveys the information.
> Support Function and Action Procedure execution
> -----------------------------------------------
>
> Key: OLINGO-450
> URL: https://issues.apache.org/jira/browse/OLINGO-450
> Project: Olingo
> Issue Type: New Feature
> Components: odata4-server
> Affects Versions: V4 4.0.0-beta-01
> Reporter: Ramesh Reddy
> Assignee: Michael Bolz
> Fix For: (Java) V4 4.0.0-beta-02
>
>
> There are no "Processor" interface designed to handle the Function or Action
> procedure invocation in V4 Java version.
> Based on current Processor interface, a target interface can look like
> {code}
> interface ProcedureProcessor extends Processor {
> void invokeFunction(ODataRequest request, ODataResponse response, UriInfo
> uriInfo, ContentType requestedContentType);
> void invokeAction(ODataRequest request, ODataResponse response, UriInfo
> uriInfo, ContentType requestedContentType);
> }
> {code}
> If we agree on the interface I can provide the patch file for implementation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
