[ https://issues.apache.org/jira/browse/OLINGO-1106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Amend resolved OLINGO-1106. ------------------------------------- Resolution: Fixed Fix Version/s: (Java) V4 4.4.0 Resolved with commit: https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=af116170a2fe89dbaef3f859e65d596f79206c4e > Custom Query options in batch request > ------------------------------------- > > Key: OLINGO-1106 > URL: https://issues.apache.org/jira/browse/OLINGO-1106 > Project: Olingo > Issue Type: Test > Components: odata4-server > Reporter: Archana Rai > Assignee: Christian Amend > Priority: Minor > Fix For: (Java) V4 4.4.0 > > Attachments: 1357b28a.diff > > > To ensure nothing breaks with the ABNF adaption/change for custom query with > $batch, we have added tests. > OData V4.0 Errata 03 already explicitly allows custom query options without > restricting this to certain request types. See > > http://docs.oasis-open.org/odata/odata/v4.0/errata03/os/complete/part1-protocol/odata-v4.0-errata03-os-part1-protocol-complete.html#_Toc453752212: > > As per the ABNF for OData V4.01 : all requests now allow custom query > options. See: > https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/4.01%20spec/ABNF/odata-abnf-construction-rules.txt?rev=1023&sc=0&isdir=0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)