[
https://issues.apache.org/jira/browse/OLINGO-872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15138689#comment-15138689
]
Frederik Zimmer commented on OLINGO-872:
----------------------------------------
I think the cause of the problem is an unclear API in
org.apache.olingo.client.api.uri.URIBuilder. It has appendOperationCallSegment
which according to the documentation can be used for actions and functions. But
I don't think this is true. It can only be used for functions and for actions
you have to use appendActionCallSegment.
I would propose to create an appendFunctionCallSegment method and deprecate
appendOperationCallSegment and correct the javadoc of
appendOperationCallSegment.
> Client-Proxy: Unbound action called as actionName() instead of actionName
> -------------------------------------------------------------------------
>
> Key: OLINGO-872
> URL: https://issues.apache.org/jira/browse/OLINGO-872
> Project: Olingo
> Issue Type: Bug
> Components: odata4-ext
> Affects Versions: (Java) V4 4.1.0
> Reporter: Frederik Zimmer
>
> When invoking an unbound action with the client-proxy framework an URL with
> .../actionName() is called. The olingo server only understands .../actionName
> which I think is correct.
> When you also think that this is a bug I can create a patch for
> org.apache.olingo.ext.proxy.commons.OperationInvocationHandler which contains
> the bug and for the incorrect testcases in org.apache.olingo.fit.Services.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
