[
https://issues.apache.org/jira/browse/OLINGO-861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15931143#comment-15931143
]
Ramesh Reddy commented on OLINGO-861:
-------------------------------------
>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.
[~rafiqkattangere] What I am saying as part of first load, it need to resolve
all the references, thus loads the references. But when loading those
references, they refer back to themselves. So, load is never finished. I do not
have reproducer for second case, I still need to fix that.
> 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)
