[
https://issues.apache.org/jira/browse/OLINGO-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14176894#comment-14176894
]
Michael Bolz commented on OLINGO-450:
-------------------------------------
Hi [~rareddy],
I created a [feature branch
(OLINGO-450_FunctionActionExecution)|https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=shortlog;h=refs/heads/OLINGO-450_FunctionActionExecution]
for easier discussions and resulting changes about this issue before we then
finally do a merge with master branch.
First look seems good, however I have to check in detail.
Some first points for discussion are:
- How we should extend the technical service (which data and separation of
processors?)
- It seems that the {{ODataJsonSerializer}} has duplicate code (but this is
probably only because of changes in master since your contribution)
As soon I have more insight (especially about the new interfaces) I will give
more feedback.
Kind regards,
Michael
> 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)
