Archana Rai created OLINGO-1079:
-----------------------------------
Summary: edmx Reference tag Issue
Key: OLINGO-1079
URL: https://issues.apache.org/jira/browse/OLINGO-1079
Project: Olingo
Issue Type: Bug
Components: odata2-core
Reporter: Archana Rai
Olingo version 2.0 validation as validation failes the edmx due to prefix
mentioned as below.
Ex:
<edmx:Edmx xmlns:edmx="http://schemas.microsoft.com/ado/2007/06/edmx";
xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata";
xmlns:sap="http://www.sap.com/Protocols/SAPData"; Version="1.0">
<edmx:Reference xmlns:edmx="http://docs.oasis-open.org/odata/ns/edmx";
Uri="https://host:port/sap/opu/odata/IWFND/CATALOGSERVICE;v=2/Vocabularies(TechnicalName='%2FIWBEP%2FVOC_COMMON',Version='0001',SAP__Origin='')/$value">
<edmx:Include Alias="Common" Namespace="com.sap.vocabularies.Common.v1"/>
</edmx:Reference>
edmx:Reference tags are not supported by the OData V2 specification.
The root Edmx element is using the OData V2 Edmx namespace with namespace
prefix edmx:
<edmx:Edmx xmlns:edmx="http://schemas.microsoft.com/ado/2007/06/edmx";
The nested Reference element is using the OData V4 Edmx namespace and redefines
the edmx: prefix
<edmx:Reference xmlns:edmx="http://docs.oasis-open.org/odata/ns/edmx";
A better prefix choice would have been edmx4: or anything except edmx:, but the
XML document is nevertheless correct.
Section 1.7 of the OData V2 Edmx specification says in
https://msdn.microsoft.com/en-us/library/dd541467.aspx
Parsers of EDMX documents ignore content that is unexpected or that cannot be
parsed.
So skipping unknown tags should be the default behavior of the Olingo Edmx
parser.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
