|
| Re: Platform URI and special chars in project name [message #416115 is a reply to message #416108] |
Fri, 18 January 2008 11:44   |
 Ed Merks
Messages: 33138
Registered: July 2009 |
Senior Member |
|
|
This is a multi-part message in MIME format.
--------------060305080407010006080608
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sascha,
You should always use
URI.createPlatformURI(iFile.getFullPath().toString(), *true*) to ensure
that special characters are encoded. For the IFile
"/a#%b/model/a#%b.ecore" it would yield
"platform:/resource/a%23%25b/a%23%25b.ecore", which is of course totally
unreadable so in general you should avoid these characters like a bad
disease. Even a space is bad enough and tends to throw all kinds of
applications for a loop. The basic Ecore things I just tried worked
fine for this scenario, but I still recommend against the practice since
in my experience far too many utilities overlook doing either the
encoding or the decoding either of which is likely to get you into
trouble...
Sascha Theves wrote:
> Hi all,
>
> we have several problems loading our model files when the project name does
> include special characters such as '#' or '%'. Thats because EMF resources
> are referenced by URIs. And in the URI implementation such special chars are
> used to separate the URI fragment etc... If you have a project with name
> 'My#Project' that confuses EMF. I think this is a general problem and not
> special to our models. Is there a workaround for the problem?
>
> Thanks in advance,
>
> Sascha
>
>
>
--------------060305080407010006080608
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Sascha,<br>
<br>
You should always use
URI.createPlatformURI(iFile.getFullPath().toString(), <b>true</b>) to
ensure that special characters are encoded. For the IFile
"/a#%b/model/a#%b.ecore" it would yield
"platform:/resource/a%23%25b/a%23%25b.ecore", which is of course
totally unreadable so in general you should avoid these characters like
a bad disease. Even a space is bad enough and tends to throw all kinds
of applications for a loop. The basic Ecore things I just tried worked
fine for this scenario, but I still recommend against the practice
since in my experience far too many utilities overlook doing either the
encoding or the decoding either of which is likely to get you into
trouble...<br>
<br>
<br>
Sascha Theves wrote:
<blockquote cite="mid:fmpqrh$j5d$1@build.eclipse.org" type="cite">
<pre wrap="">Hi all,
we have several problems loading our model files when the project name does
include special characters such as '#' or '%'. Thats because EMF resources
are referenced by URIs. And in the URI implementation such special chars are
used to separate the URI fragment etc... If you have a project with name
'My#Project' that confuses EMF. I think this is a general problem and not
special to our models. Is there a workaround for the problem?
Thanks in advance,
Sascha
</pre>
</blockquote>
<br>
</body>
</html>
--------------060305080407010006080608--
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
|
| Re: Platform URI and special chars in project name [message #416131 is a reply to message #416128] |
Fri, 18 January 2008 15:21 |
Ed Merks
Messages: 33138
Registered: July 2009 |
Senior Member |
|
|
This is a multi-part message in MIME format.
--------------010608050304020002050400
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sasacha,
EMF does all such encoding and decoding automatically. That's why we
deprecated the one argument URI.createPlatformResourceURI to force all
users to consider that they should call the new one with true (we got
complaints when we did this in the existing method). You'll find all
uses both generated and in the framework use the two argument for and
specify true. The toPlatformString will do the decoding and we always
use that too. The problem with encoding is you have to be so careful
not to do it too many times...
Sascha Theves wrote:
> Hi Ed,
>
> you are right, we can encode the URI when creating the instance and
> then loading our models with that URI. But as you said many tools
> doesn`t worry much about encoding/decoding of URIs and that results in
> several exceptions in our application. The problem is we cannot
> prevent the user renaming its project to an invalid name. So in my
> opinion you cannot prevent such exceptions. Am I right? Maybe EMF
> could encode/decode such URIs automatically so clients doesn`t worry
> about it?
>
> But whatever - thanks for your answer and quick help!!! The support in
> EMF newsgroup is amazing!
>
> Greets
>
> Sascha
>
--------------010608050304020002050400
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Sasacha,<br>
<br>
EMF does all such encoding and decoding automatically. That's why we
deprecated the one argument URI.createPlatformResourceURI to force all
users to consider that they should call the new one with true (we got
complaints when we did this in the existing method). You'll find all
uses both generated and in the framework use the two argument for and
specify true. The toPlatformString will do the decoding and we always
use that too. The problem with encoding is you have to be so careful
not to do it too many times...<br>
<br>
<br>
Sascha Theves wrote:
<blockquote cite="mid:fmqeeq$3m6$1@build.eclipse.org" type="cite">
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<meta content="MSHTML 6.00.6000.16544" name="GENERATOR">
<style></style>
<div><font face="Arial" size="2">Hi Ed,</font></div>
<div> </div>
<div><font face="Arial" size="2">you are right, we can encode the URI
when creating the instance and then loading our models with that URI.
But as you said many tools doesn`t worry much about encoding/decoding
of URIs and that results in several exceptions in our application. The
problem is we cannot prevent the user renaming its project to an
invalid name. So in my opinion you cannot prevent such exceptions. Am I
right? Maybe EMF could encode/decode such URIs automatically so clients
doesn`t worry about it?</font></div>
<div> </div>
<div><font face="Arial" size="2">But whatever - thanks for your
answer and quick help!!! The support in EMF newsgroup is amazing!</font></div>
<div> </div>
<div><font face="Arial" size="2">Greets</font></div>
<div> </div>
<div><font face="Arial" size="2">Sascha</font></div>
<br>
</blockquote>
<br>
</body>
</html>
--------------010608050304020002050400--
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Powered by
FUDForum. Page generated in 0.03536 seconds
] 
Search
Help
Register
Login
Home
