[jira] [Commented] (OLINGO-450) Support Function and Action Procedure execution

["Michael Bolz (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OLINGO-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198364#comment-14198364 ] 

Michael Bolz commented on OLINGO-450:
-------------------------------------

Hi all,

I have done a merge of your contribution with the current master branch (see [this commit|https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=eb1afd62a1046f25f0484318845f9de60a90c618]).
Unfortunately it was a lot more changes as I thought and some tests in {{ProcedureITCase}} are broken. 
Especially because the ContentNegotiation has changed through introduction of a new {{RepresentationType}} enum.

During the introduction of this {{RepresentationType}} a discussion has started about re-factoring the {{Processor}} interfaces.
The new idea is to create an own {{*Processor}} interface for each {{RepresentationType}} which then has the according HTTP methods (in form of read/write/..).
As a result we don’t have explicit {{ProcedureProcessor}} because during the dispatching the {{ReturnType}} of an e.g. Function is evaluated and the call is than processed by the according e.g. {{EntityProcessor}} or {{EntitySetProcessor}} or {{SomeOtherProcessor}}.

Till start of next week I also want to create an JIRA-Issue to discuss this change (or write mail on dev mailing list).
As long as the decision is open I would wait with fixing the currently “ignored ProcedureITCase tests” and according implementation.

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)