phdmohans / odata4j

Automatically exported from code.google.com/p/odata4j
0 stars 0 forks source link

Invalid FeedCustomizationMapping for navigation property feed entries #146

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?

ODataConsumer c = 
ODataJerseyConsumer.newBuilder("http://services.odata.org/OData/OData.svc/").bui
ld();
OQueryRequest<OEntity> query = 
c.getEntities("Categories").nav(OEntityKey.create(0), "Products"); 

-> Product type maps Name/Description properties to 
SyndicationTitle/SyndicationSummary
-> OEntity does not contain properties for "Name"/"Description"

What is the expected output? What do you see instead?

Properties for product name/description should be available and contain the 
values from SyndicationTitle/SyndicationSummary. Instead OEntity doesn't 
contain property instances for Name/Description at all.

What version of the product are you using? On what operating system?

odata4j-0.6

Please provide any additional information below.

ODataJerseyConsumer provides an invalid FeedCustomizationMapping to 
AtomFeedFormatParser for feed entry collections retrieved through a navigation 
property. If the assiociated enitity type maps properties to 
SyndicationTitle/SyndicationSummary, AtomFeedFormatParser is unable to resolve 
the correct entity property to set the mapped values.

In this case a FeedCustomizationMapping instance for type "Category" (first 
collection in resource path) is propagated to AtomFeedFormatParser while the 
correct mapping would be for the linked "Product" type.

Original issue reported on code.google.com by manuel.r...@gmail.com on 15 Mar 2012 at 4:24

GoogleCodeExporter commented 9 years ago
We are running into this issue with odata4j v7 as well. Kindly look into this 
asap.

Original comment by kapil8...@gmail.com on 4 Oct 2012 at 5:50

GoogleCodeExporter commented 9 years ago
I am also facing the same issue with odata4j v7 as well. please revert ASAP.

Original comment by parashar...@gmail.com on 4 Oct 2012 at 5:52

GoogleCodeExporter commented 9 years ago
Taking a look, these FeedCustomizationMappings should really be a function of 
the metadata instead of being computed only in the consumer and passed around 
separately (and incorrectly).

Original comment by john.spurlock on 10 Nov 2012 at 10:08

GoogleCodeExporter commented 9 years ago
This issue was closed by revision c9275957f2f0.

Original comment by john.spurlock on 10 Nov 2012 at 11:25