Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » EMF » [EMFT] WorkspaceSynchronizer doesn't checks that URI is not a platform resource URI
[EMFT] WorkspaceSynchronizer doesn't checks that URI is not a platform resource URI [message #757948] Wed, 16 November 2011 14:58 Go to next message
Esteban Dugueperoux is currently offline Esteban DugueperouxFriend
Messages: 472
Registered: July 2009
Senior Member
Hi,

In the context of CDO and GMF, we have many calls to
WorkspaceSynchronizer.getFile(Resource) with CDOResource and custom
resources (some using a custom URI with a "memory" scheme) but we get
some exceptions in 3.6 for example :

org.eclipse.core.runtime.CoreException: No file system is defined for
scheme: memory
at org.eclipse.core.internal.filesystem.Policy.error(Policy.java:55)
at org.eclipse.core.internal.filesystem.Policy.error(Policy.java:50)
at
org.eclipse.core.internal.filesystem.InternalFileSystemCore.getFileSystem(InternalFileSystemCore.java:65)
at
org.eclipse.core.internal.filesystem.InternalFileSystemCore.getStore(InternalFileSystemCore.java:107)
at org.eclipse.core.filesystem.EFS.getStore(EFS.java:470)
at
org.eclipse.core.internal.localstore.FileSystemResourceManager.findLinkedResourcesPaths(FileSystemResourceManager.java:142)
at
org.eclipse.core.internal.localstore.FileSystemResourceManager.allPathsForLocationNonCanonical(FileSystemResourceManager.java:124)
at
org.eclipse.core.internal.localstore.FileSystemResourceManager.allPathsForLocation(FileSystemResourceManager.java:62)
at
org.eclipse.core.internal.localstore.FileSystemResourceManager.allResourcesFor(FileSystemResourceManager.java:216)
at
org.eclipse.core.internal.resources.WorkspaceRoot.findFilesForLocationURI(WorkspaceRoot.java:113)
at
org.eclipse.core.internal.resources.WorkspaceRoot.findFilesForLocationURI(WorkspaceRoot.java:104)
at
org.eclipse.emf.workspace.util.WorkspaceSynchronizer.getFile(WorkspaceSynchronizer.java:357)
at
org.eclipse.emf.workspace.util.WorkspaceSynchronizer.getFile(WorkspaceSynchronizer.java:270)

Indeed at line 360 of WorkspaceSynchronizer where we have result == null
we don't checks that the normalized URI is a platform resource URI.

Is it make sense to raise a bugzilla entry?

Best Regards.

Report message to a moderator

Re: [EMFT] WorkspaceSynchronizer doesn't checks that URI is not a platform resource URI [message #757951 is a reply to message #757948] Thu, 17 November 2011 06:48 Go to previous messageGo to next message
Ed Merks is currently offline Ed MerksFriend
Messages: 33140
Registered: July 2009
Senior Member
Esteban,

I thought this was fixed in the last release, but maybe not.

On 16/11/2011 3:58 PM, Esteban Dugueperoux wrote:
> Hi,
>
> In the context of CDO and GMF, we have many calls to
> WorkspaceSynchronizer.getFile(Resource) with CDOResource and custom
> resources (some using a custom URI with a "memory" scheme) but we get
> some exceptions in 3.6 for example :
>
> org.eclipse.core.runtime.CoreException: No file system is defined for
> scheme: memory
> at org.eclipse.core.internal.filesystem.Policy.error(Policy.java:55)
> at org.eclipse.core.internal.filesystem.Policy.error(Policy.java:50)
> at
> org.eclipse.core.internal.filesystem.InternalFileSystemCore.getFileSystem(InternalFileSystemCore.java:65)
> at
> org.eclipse.core.internal.filesystem.InternalFileSystemCore.getStore(InternalFileSystemCore.java:107)
> at org.eclipse.core.filesystem.EFS.getStore(EFS.java:470)
> at
> org.eclipse.core.internal.localstore.FileSystemResourceManager.findLinkedResourcesPaths(FileSystemResourceManager.java:142)
> at
> org.eclipse.core.internal.localstore.FileSystemResourceManager.allPathsForLocationNonCanonical(FileSystemResourceManager.java:124)
> at
> org.eclipse.core.internal.localstore.FileSystemResourceManager.allPathsForLocation(FileSystemResourceManager.java:62)
> at
> org.eclipse.core.internal.localstore.FileSystemResourceManager.allResourcesFor(FileSystemResourceManager.java:216)
> at
> org.eclipse.core.internal.resources.WorkspaceRoot.findFilesForLocationURI(WorkspaceRoot.java:113)
> at
> org.eclipse.core.internal.resources.WorkspaceRoot.findFilesForLocationURI(WorkspaceRoot.java:104)
> at
> org.eclipse.emf.workspace.util.WorkspaceSynchronizer.getFile(WorkspaceSynchronizer.java:357)
> at
> org.eclipse.emf.workspace.util.WorkspaceSynchronizer.getFile(WorkspaceSynchronizer.java:270)
>
> Indeed at line 360 of WorkspaceSynchronizer where we have result ==
> null we don't checks that the normalized URI is a platform resource URI.
>
> Is it make sense to raise a bugzilla entry?
>
> Best Regards.
>
>

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Re: [EMFT] WorkspaceSynchronizer doesn't checks that URI is not a platform resource URI [message #757956 is a reply to message #757951] Thu, 17 November 2011 10:38 Go to previous message
Esteban Dugueperoux is currently offline Esteban DugueperouxFriend
Messages: 472
Registered: July 2009
Senior Member
Hi Ed,

It don't seems fixed on trunk, I have created
https://bugs.eclipse.org/bugs/show_bug.cgi?id=364005


On 17/11/2011 07:48, Ed Merks wrote:
> Esteban,
>
> I thought this was fixed in the last release, but maybe not.
>
> On 16/11/2011 3:58 PM, Esteban Dugueperoux wrote:
>> Hi,
>>
>> In the context of CDO and GMF, we have many calls to
>> WorkspaceSynchronizer.getFile(Resource) with CDOResource and custom
>> resources (some using a custom URI with a "memory" scheme) but we get
>> some exceptions in 3.6 for example :
>>
>> org.eclipse.core.runtime.CoreException: No file system is defined for
>> scheme: memory
>> at org.eclipse.core.internal.filesystem.Policy.error(Policy.java:55)
>> at org.eclipse.core.internal.filesystem.Policy.error(Policy.java:50)
>> at
>> org.eclipse.core.internal.filesystem.InternalFileSystemCore.getFileSystem(InternalFileSystemCore.java:65)
>>
>> at
>> org.eclipse.core.internal.filesystem.InternalFileSystemCore.getStore(InternalFileSystemCore.java:107)
>>
>> at org.eclipse.core.filesystem.EFS.getStore(EFS.java:470)
>> at
>> org.eclipse.core.internal.localstore.FileSystemResourceManager.findLinkedResourcesPaths(FileSystemResourceManager.java:142)
>>
>> at
>> org.eclipse.core.internal.localstore.FileSystemResourceManager.allPathsForLocationNonCanonical(FileSystemResourceManager.java:124)
>>
>> at
>> org.eclipse.core.internal.localstore.FileSystemResourceManager.allPathsForLocation(FileSystemResourceManager.java:62)
>>
>> at
>> org.eclipse.core.internal.localstore.FileSystemResourceManager.allResourcesFor(FileSystemResourceManager.java:216)
>>
>> at
>> org.eclipse.core.internal.resources.WorkspaceRoot.findFilesForLocationURI(WorkspaceRoot.java:113)
>>
>> at
>> org.eclipse.core.internal.resources.WorkspaceRoot.findFilesForLocationURI(WorkspaceRoot.java:104)
>>
>> at
>> org.eclipse.emf.workspace.util.WorkspaceSynchronizer.getFile(WorkspaceSynchronizer.java:357)
>>
>> at
>> org.eclipse.emf.workspace.util.WorkspaceSynchronizer.getFile(WorkspaceSynchronizer.java:270)
>>
>>
>> Indeed at line 360 of WorkspaceSynchronizer where we have result ==
>> null we don't checks that the normalized URI is a platform resource URI.
>>
>> Is it make sense to raise a bugzilla entry?
>>
>> Best Regards.
>>
>>

Report message to a moderator

Previous Topic:emf-merge.xml - what does $$ mean and other questions
Next Topic:Teneo - Oracle Sequence
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Wed Apr 24 19:25:35 GMT 2024

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

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

Back to the top

Sign up to our Newsletter

A fresh new issue delivered monthly