[jira] [Updated] (OLINGO-872) Client-Proxy: Unbound action called as actionName() instead of actionName

["Frederik Zimmer (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OLINGO-872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Frederik Zimmer updated OLINGO-872:
-----------------------------------
    Attachment: OLINGO872-Unbound-action-called-as-actionName-instea.patch

Hi Christian,

I've attached a patch for the incorrect use of appendOperationCallSegment. What about the API change I proposed? Should I also submit a patch for this? In a seperate issue?

Best Regards,
Frederik

> 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
>         Attachments: OLINGO872-Unbound-action-called-as-actionName-instea.patch
>
>
> 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)