|
|
|
Re: Proxy Resolution among Resources [message #1008901 is a reply to message #1008783] |
Thu, 14 February 2013 05:04 |
Ed Merks Messages: 33137 Registered: July 2009 |
Senior Member |
|
|
Markus,
Note that even an absolute file URI could be problematic if the
underlying file path itself isn't an absolute file system path.
When an attempt to resolve a proxy occurs, ResourceSet.getEObject will
be called with the proxy's URI. This will call ResourceSet.getResource
with the URI with the fragment trimmed. So your resource set will
definitely contain a resource with the URI [abspathtoresourceA], if
proxy resolution is attempted. That could fail to load for some reason,
but the cause of the failure will be recorded in Resource.getErrors.
Assuming it loads properly, Resource.getEObject will be called with the
fragment. If the resource is able to find the object with that
fragment, it will be returned and all will work well; if it returns
null, the proxy will fail to resolve. So, somewhere along this path,
something is failing for you. Setting breakpoints in
ResourceSetImpl.getResource and ResourceImpl.getEObject should help you
track down what's going wrong in your scenario.
On 13/02/2013 9:58 PM, Markus Riedl wrote:
> The URI's are absolute and the URI - kind is fileURI. In my case there
> is no XML, "I" parse a file into ECore-Representation, nonetheless the
> proxies should resolve ... the proxy - uri looks like:
> [abspathtoresourceA]#EMFTEXT_INTERNAL_URI_FRAGMENT_0_A, if this gives
> you some hint
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Powered by
FUDForum. Page generated in 0.03376 seconds