[
https://issues.apache.org/jira/browse/OLINGO-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14103375#comment-14103375
]
Challen commented on OLINGO-327:
--------------------------------
Hi Ralf, thank you, now the java client by default supports only qualified name
as function name. the change I made some time ago was to add a configuration
flag for using short name, it requires the user to explicitly call
config.setUseUrlOperationFQN(final boolean value), or fully qualified name will
still be used.
https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=f40643f92ecb43b2a135fc413eba318801ae8744
> make client supports shorter operation name in url (not protocol standard)
> --------------------------------------------------------------------------
>
> Key: OLINGO-327
> URL: https://issues.apache.org/jira/browse/OLINGO-327
> Project: Olingo
> Issue Type: Bug
> Components: odata4-client
> Affects Versions: V4 4.0.0-beta-01
> Reporter: Challen
> Assignee: Challen
> Fix For: V4 4.0.0-beta-01
>
>
> e.g. make client be able to send request like
> http://host/service/Customers(2)/IncreaseSalary , while also supporting
> http://host/service/Customers(2)/NS1.Model.IncreaseSalary which is the
> standard OData V4 way
--
This message was sent by Atlassian JIRA
(v6.2#6252)
