Eclipse Community Forums: TMF (Xtext) » ImportURI scoping case sensitive

Home » Modeling » TMF (Xtext) » ImportURI scoping case sensitive("Imported resource could not be found" error due to scoping case sensitive)

Show: Today's Messages :: Show Polls :: Message Navigator

ImportURI scoping case sensitive [message #1008112]

Sat, 09 February 2013 01:02

Hao Xie
Messages: 64
Registered: January 2013

Member

I used the following fragments in mwe2 file.

// scoping and exporting API
fragment = scoping.ImportURIScopingFragment {
ignoreCase = true
}
fragment = exporting.SimpleNamesFragment {}

In the xtext file, I used the following grammar

IncludeFile: "include" importURI=STRING;

The text editor still seems to be case sensitive for included file string. When a URI path name matches with file path name but case doesn't match, an error of "Imported resource could not be found" occurs in the text editor. Only when both the name and case are matched, no error will occur.

Did I miss anything in my implementation?

Report message to a moderator

Re: ImportURI scoping case sensitive [message #1008269 is a reply to message #1008112]

Sun, 10 February 2013 16:37

Jan Kohnlein
Messages: 572
Registered: July 2009

Senior Member

Case insensitive linking refers to model element names, not to file
names. Many file systems are case insensitive by default, but Xtext does
not add anything in this regard.

Am 09.02.13 07:03, schrieb Hao Xie:
> I used the following fragments in mwe2 file.
>
> // scoping and exporting API
> fragment = scoping.ImportURIScopingFragment {
> ignoreCase = true
> } fragment = exporting.SimpleNamesFragment {}
>
>
> In the xtext file, I used the following grammar
>
> IncludeFile: "include" importURI=STRING;
>
>
> The text editor still seems to be case sensitive for included file
> string. When a URI path name matches with file path name but case
> doesn't match, an error of "Imported resource could not be found" occurs
> in the text editor. Only when both the name and case are matched, no
> error will occur.
> Did I miss anything in my implementation?

--
Need professional support for Eclipse Modeling?
Go visit: http://xtext.itemis.com

Report message to a moderator

Re: ImportURI scoping case sensitive [message #1008314 is a reply to message #1008269]

Mon, 11 February 2013 16:32

Hao Xie
Messages: 64
Registered: January 2013

Member

Windows file system should be case insensitive. But I don't know why importUrl doesn't work if case doesn't match.

Report message to a moderator

Re: ImportURI scoping case sensitive [message #1008383 is a reply to message #1008314]

Tue, 12 February 2013 04:09

Jan Kohnlein
Messages: 572
Registered: July 2009

Senior Member

That could be EMF's URIs or Eclpise's filesystem.

Am 11.02.13 22:32, schrieb Hao Xie:
> Windows file system should be case insensitive. But I don't know why
> importUrl doesn't work if case doesn't match.

--
Need professional support for Eclipse Modeling?
Go visit: http://xtext.itemis.com

Report message to a moderator

Re: ImportURI scoping case sensitive [message #1008480 is a reply to message #1008383]

Tue, 12 February 2013 11:52

Hao Xie
Messages: 64
Registered: January 2013

Member

Thank you. I guess I have to spell the URI name with case matched in my language.

Report message to a moderator

Previous Topic:	Validate against model structure
Next Topic:	Generating from BNF Grammar at runtime

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sat May 25 11:00:34 EDT 2013