Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » TMF (Xtext) » ImportURI scoping case sensitive("Imported resource could not be found" error due to scoping case sensitive)
ImportURI scoping case sensitive [message #1008112] Sat, 09 February 2013 06:02 Go to next message
Hao Xie is currently offline Hao XieFriend
Messages: 68
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?
Re: ImportURI scoping case sensitive [message #1008269 is a reply to message #1008112] Sun, 10 February 2013 21:37 Go to previous messageGo to next message
Jan Koehnlein is currently offline Jan KoehnleinFriend
Messages: 760
Registered: July 2009
Location: Hamburg
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


---
Get professional support from the Xtext committers at www.typefox.io
Re: ImportURI scoping case sensitive [message #1008314 is a reply to message #1008269] Mon, 11 February 2013 21:32 Go to previous messageGo to next message
Hao Xie is currently offline Hao XieFriend
Messages: 68
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.
Re: ImportURI scoping case sensitive [message #1008383 is a reply to message #1008314] Tue, 12 February 2013 09:09 Go to previous messageGo to next message
Jan Koehnlein is currently offline Jan KoehnleinFriend
Messages: 760
Registered: July 2009
Location: Hamburg
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


---
Get professional support from the Xtext committers at www.typefox.io
Re: ImportURI scoping case sensitive [message #1008480 is a reply to message #1008383] Tue, 12 February 2013 16:52 Go to previous message
Hao Xie is currently offline Hao XieFriend
Messages: 68
Registered: January 2013
Member
Thank you. I guess I have to spell the URI name with case matched in my language.
Previous Topic:Validate against model structure
Next Topic:Generating from BNF Grammar at runtime
Goto Forum:
  


Current Time: Thu Apr 25 15:52:47 GMT 2024

Powered by FUDForum. Page generated in 0.03169 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top