| [news.eclipse.technology.epf] Re: Getting RoleSets from XMI files |
Quentin,
Comments below.
The initial resource URI that I load in my program is (actualy obviously) the path of the xmi file I loaded : model.xmi.This is a relative URI, not an absolute one, so relative references within that resource will not likely be handled correctly. It would be good to see the actual value that you're using.
I don't know anything about uma schemes. I guess human readability wasn't a concern...
And about the proxyURI of the guidelines, it's uma links like this one for example : uma://_wTuT0MmrEdyxNoaGNtevxw#_GgH6wOn8EdyMKb-pMuCr4g
That method uses just the fragment, i.e., "_GgH6wOn8EdyMKb-pMuCr4g". I would imagine that even if the proxy fails to resolve (you can cast to InternalEObject and use eProxyURI to see the URI of the proxy that's failing to resolve) you'd still have a resource with URI "uma://_wTuT0MmrEdyxNoaGNtevxw". If you called getErrors on that resource, it will likely indicate why it failed to load. It sounds like you might well need to be hooking up some special support to handle uma: scheme, but that's an probably EPF question I can't answer...
I've tried to use resource.getEOBject("the URI") but I couldn't get any object : always 'null'.
Well, you mustn't have the dependencies right.
In what concerns the classpath, I've already tried to modify my graphical plugin dependencies, but I couldn't get it to work. I always get the error message "Error creating the view", because of the java.lang.NoClassDefFoundError exception.
Try using "Required Plug-ins" instead.
In the PDE (Plugin Development Environment), I can't add my library in "Imported Packages". And when I try to add it myself directly into the MANIFEST.MF, with "Import-Package com.(...).library", I get this error : "No available bundle exports package 'com.(...).library'.
Thank you,
Quentin