olingo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ramesh Reddy (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (OLINGO-1271) Absolute Context URL with Service Dispatcher
Date Thu, 21 Jun 2018 21:45:00 GMT

     [ https://issues.apache.org/jira/browse/OLINGO-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ramesh Reddy resolved OLINGO-1271.
----------------------------------
       Resolution: Fixed
    Fix Version/s: (Java) V4 4.5.0

resolved with commit https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=1fef3a131ea4cc334151a7f10b67cab6bb424239

> 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
>            Assignee: Ramesh Reddy
>            Priority: Major
>             Fix For: (Java) V4 4.5.0
>
>
> 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)

Mime
View raw message