[
https://issues.apache.org/jira/browse/OLINGO-861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15930997#comment-15930997
]
rafiqkattangere commented on OLINGO-861:
----------------------------------------
[~rareddy] When you have hundreds of schema files defining a complex data
model, then having nested references circle back may be unavoidable. In this
case itself, if we get rid of circling references, the schema parsing would
fail with unknown Type definitions.
So I also don't know the solution. According to me, the parser has knowledge of
the producer service its loading/validating for. Globally (at producer service)
we need to make sure once loaded/validated schema shouldn't get loaded again.
Can we explore that option. Like in this case, we already loaded
Message_v1.xml, though it came back again in circle, the second iteration could
have continued pointing to the old load. I don't know how this would work, but
you understand it better. Without resolving this issue, I cannot use this
library for my service!
Thanks for all the help.
> 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)
