[
https://issues.apache.org/jira/browse/OLINGO-861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15938331#comment-15938331
]
rafiqkattangere commented on OLINGO-861:
----------------------------------------
BTW I have raised this issue with Redfish developers. Apparently the Odata spec
says that the parser should not assume the references can be recursively
parsed.
And these are the responses I got.
See the OData CSDL spec section 3.3: "Note: referencing documents is not
recursive. Only named elements defined in directly referenced documents can be
used within the schema. However, those elements may in turn include elements
defined in schemas referenced by their defining schema."
"essentially when you're working in a schema file, you only go one level deep
of inclusions. You don't include the schema files of the included files. This
allows for cyclic inclusions."
> MetaDataParser unable to build EdmProvider from Edmx files with references
> --------------------------------------------------------------------------
>
> Key: OLINGO-861
> URL: https://issues.apache.org/jira/browse/OLINGO-861
> Project: Olingo
> Issue Type: Bug
> Components: odata4-server
> Affects Versions: (Java) V4 4.1.0
> Reporter: VIJAYASIMHA R NAGA
> Assignee: Ramesh Reddy
> Fix For: (Java) V4 4.2.0
>
> Attachments: MyODataDemoService.zip, nestedreference.zip,
> ServiceRoot.xml
>
>
> Unable to build an EdmProvider from Edmx files with references to external
> name spaces, (Method "readReference" in MetaDataParser.java from
> server-core-ext library has a TODO remark to deal with this)
> Ex: Having the below reference included in an Edmx file <edmx:Reference
> Uri="http://docs.oasis-open.org/odata/odata/v4.0/cs01/vocabularies/Org.OData.Core.V1.xml";>
> <edmx:Include Namespace="Org.OData.Core.V1" Alias="OData"/> </edmx:Reference>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
