[ 
https://issues.apache.org/jira/browse/OLINGO-861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15139693#comment-15139693
 ] 

VIJAYASIMHA R NAGA edited comment on OLINGO-861 at 2/9/16 8:46 PM:
-------------------------------------------------------------------

Hi Ramesh, I've attached the Edmx file I've used for my testing, The sample web 
project I am using for this only has the Servlet code which I am attaching 
here, I deployed this into my local tomcat instance & then ran the metadata url 
"http://localhost:8080/odata-service-sample-v1-1.0/root.svc/$metadata";

My observation with the current way of implementation is that unless the 
schemas from the included files are added to the edm, it would not help 
resolving their references in the current/actual Edmx file, but this way the 
metadata doc will be bloated with all of the included schemas, to avoid this 
somehow there should be a way to isolate the reference schemas from the 
current/actual schema.

Also, the references are all only allowed to pointed to http urls, I wish there 
were ways to be able to refer to Edmx files in local path too!


was (Author: nvsreddy):
Hi Ramesh, I've attached the Edmx file I've used for my testing, The sample web 
project I am using for this only has the Servlet code which I am attaching 
here, I deployed this into my local tomcat instance & then ran the metadata url 
"http://localhost:8080/odata-service-sample-v1-1.0/root.svc/$metadata";

My observation with the current way of implementation is that unless the 
schemas from the included files are added to the edm, it would not help 
resolving their references in the current/actual Edmx file

> 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, 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.4#6332)

Reply via email to