Bug 1316501 - OData - $ref after $expand does not work
OData - $ref after $expand does not work
Product: JBoss Data Virtualization 6
Classification: JBoss
Component: Teiid (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ER2
: 6.3.0
Assigned To: Van Halbert
Juraj Duráni
Depends On:
  Show dependency treegraph
Reported: 2016-03-10 06:18 EST by Juraj Duráni
Modified: 2016-08-24 07:38 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-08-24 07:38:20 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
JBoss Issue Tracker TEIID-4059 Major Resolved OData - $ref after $expand does not work 2016-05-27 07:18 EDT

  None (edit)
Description Juraj Duráni 2016-03-10 06:18:12 EST
Description of problem:
If user declares $ref after $expand, OData service should return inline references to entities instead of whole entities.

*URL:* http://localhost:8080/odata4/olingo_basic/Source/Customers/?$expand=Orders_FK0/$ref
<a:link rel="http://docs.oasis-open.org/odata/ns/related/Orders_FK0" title="Orders_FK0" href="http://localhost:8080/odata4/olingo_basic/Source/Customers(1)/Orders_FK0">
*Expected result:* 
<a:link rel="http://docs.oasis-open.org/odata/ns/related/Orders_FK0" title="Orders_FK0" href="http://localhost:8080/odata4/olingo_basic/Source/Customers(1)/Orders_FK0">
      <m:ref id="http://localhost:8080/odata4/olingo_basic/Source/Orders(1)"/>

See http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part1-protocol/odata-v4.0-errata02-os-part1-protocol-complete.html#_Toc406398298
Comment 1 JBoss JIRA Server 2016-03-23 09:15:17 EDT
Ramesh Reddy <rareddy@jboss.org> updated the status of jira TEIID-4059 to Coding In Progress
Comment 2 JBoss JIRA Server 2016-03-29 10:06:14 EDT
Ramesh Reddy <rareddy@jboss.org> updated the status of jira TEIID-4059 to Resolved

Note You need to log in before you can comment on or make changes to this bug.