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-1186) OData 4 parsing older service metadata
Date Fri, 03 Aug 2018 21:36:00 GMT

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

Ramesh Reddy resolved OLINGO-1186.
----------------------------------
    Resolution: Fixed

Fixed with commit [https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=c7664d4cbd6358a9031a1d7355850e4f24179078]

 

[~shawkins] The DataServiceVersion is OData V2 construct, not defined in the V4. However,
the client can now do

{code}
metadata.getEdmversion()
{code}

which should give the OData version number that can be checked against. Either case I believe
DataServiceVersion in V2 was designed to get the Schema/Service version which is application
specific.

> OData 4 parsing older service metadata
> --------------------------------------
>
>                 Key: OLINGO-1186
>                 URL: https://issues.apache.org/jira/browse/OLINGO-1186
>             Project: Olingo
>          Issue Type: Bug
>          Components: odata4-client
>            Reporter: Steven Hawkins
>            Assignee: Ramesh Reddy
>            Priority: Major
>             Fix For: (Java) V4 4.5.0
>
>
> If you point the OData 4 client to older metadata, for example http://services.odata.org/Northwind/Northwind.svc/$metadata
the result will be metadata with null values where non-null is expected.
> {code}
> ClientODataDeserializerImpl deserializer = 
>                         new ClientODataDeserializerImpl(false, ContentType.APPLICATION_XML);
> XMLMetadata serviceMatadata = deserializer.toMetadata(out.getBinaryStream());
> CsdlSchema csdlSchema = metadata.getSchemas().get(0);
> CsdlEntityContainer container = csdlSchema.getEntityContainer(); 
> //container is null
> {code}
> It would be good if XMLMetadata exposed the DataServices version information, or if Olingo
could do some check of them when parsing to validate expectations. 
> This was also captured as https://issues.jboss.org/browse/TEIID-5071



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message