[
https://issues.apache.org/jira/browse/OLINGO-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14104957#comment-14104957
]
Challen commented on OLINGO-327:
--------------------------------
MS exchange OData service is doing that now: supports ~/Message( .... )/Send,
not the standard OData url ~/Message( .... )/<the ms exchange odata
namespace>.Send , I guess the service should still map it to <the ms exchange
odata namespace>.Send , but looks 'better' than the long name since user
already knows it is MS exchange OData service so may not want to always write
<the ms exchange odata namespace>.
> 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)