[
https://issues.apache.org/jira/browse/OLINGO-861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15929975#comment-15929975
]
Ramesh Reddy commented on OLINGO-861:
-------------------------------------
[~rafiqkattangere] got it, reproduced. I see that there cycle in the schema
resolution.
Message_v1.xml ---> RedfishExtensions_v1.xml -->Settings_v1.xml -->
Message_v1.xml
That seems wrong to have dependency setup in circular fashion. I could delay
/skip loading of a actively loading schema to avoid the recursion, but schemas
are resolved as they are loaded, that means the process never finishes or ends
up in error for not able to resolve. Not sure yet what the fix needs to be? My
guess is either RedFish or your usage of RedFish is wrong? Can you ask the
RedFish community what is their recommendation?
> 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)
