[teiid-issues] [JBoss JIRA] (TEIID-5343) Enable absolute URI on context definition of EntitySets when using ODATA

[Rafael Sampaio (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-5343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13596269#comment-13596269 ] 

Rafael Sampaio commented on TEIID-5343:
---------------------------------------

Hi there Ramesh, sorry for the delay.
The change applied on https://issues.apache.org/jira/browse/OLINGO-1271 does fixes the reported problem and comunication with MS products runs smoothly. Thanks a lot.

> Enable absolute URI on context definition of EntitySets when using ODATA
> ------------------------------------------------------------------------
>
>                 Key: TEIID-5343
>                 URL: https://issues.jboss.org/browse/TEIID-5343
>             Project: Teiid
>          Issue Type: Enhancement
>          Components: OData
>    Affects Versions: 10.2.1
>            Reporter: Rafael Sampaio
>            Assignee: Ramesh Reddy
>             Fix For: 11.1
>
>
> Hi all you TEIID guys.
> As reported on [OLINGO-1025|https://issues.apache.org/jira/browse/OLINGO-1025], integrating to MS OData consumers (ie. PowerBI/PowerQuery) gives the "should be an absolute Uri" error.
> The proposed solution in the JIRA is implementing a Processor for any given EntityType. Browsing through the code i see TEIID uses the ServiceHandler approach, instead of processor and it also has a Custom JSON Odata Serializer.
> I see that the Default JSON serializer, when serializing entity collections uses the ContextURL to generate the context metadata for the EntityCollection, but by default it does not contain the service root, since it comes from static DataRequest.buildEntitySetContextURL(olingo) method.
> Would be nice if we could choose this behavior through a init param in the odata deployment. 
> Thanks in advance.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)