You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@olingo.apache.org by "Ramesh Reddy (JIRA)" <ji...@apache.org> on 2018/06/21 20:05:00 UTC

[jira] [Created] (OLINGO-1271) Absolute Context URL with Service Dispatcher

Ramesh Reddy created OLINGO-1271:
------------------------------------

             Summary: Absolute Context URL with Service Dispatcher
                 Key: OLINGO-1271
                 URL: https://issues.apache.org/jira/browse/OLINGO-1271
             Project: Olingo
          Issue Type: Improvement
          Components: odata4-server
            Reporter: Ramesh Reddy


As reported on 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.6.3#76005)