[
https://issues.apache.org/jira/browse/OLINGO-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198530#comment-14198530
]
Ramesh Reddy commented on OLINGO-450:
-------------------------------------
Sorry, I thought the above is already implemented. I see that you are proposing
the change.
Ok, I see. Instead of the execution types for processor interfaces will be
based on the return types. This could be a good thing, it will generate more
fine grained interfaces and tell implementer exactly what the return type is.
The URL already tell us that much along with the metadata. Not only that, the
service implementer can be completely shielded from generating the
"contrext-url", as I saw was one of the most painful things to figure out for
each service. With this change, it can be part of the framework itself (IMO
this is must have).
> 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)
