[
https://issues.apache.org/jira/browse/OLINGO-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199823#comment-14199823
]
Michael Bolz commented on OLINGO-450:
-------------------------------------
Hi [~rareddy],
sorry for the confusion about "already implemented".
During the merge I saw that I started to "fix parts which will surely will
change after a processor refactoring".
Because of that I wanted to wait for a decision about the processor interfaces.
For the processor refactoring I create an issue and start a discussion on the
dev mailing list.
But as I see you are in the same opinion that the processor interfaces based on
return types could be a good decision.
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)
